Acuity Scheduling vs Calendly for AI agents
As of 11 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Acuity Scheduling it was stopped at sign up (blocked), with Calendly it was stopped at sign up (needs a human).
- Find: Some docs for agents: llms.txt and an OpenAPI.
- Access: Signs up sometimes.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent sign up on its own
Needs a person: Acuity Scheduling publishes agent-friendly docs, llms.txt and an OpenAPI spec, but a person must sign up, verify and make the key by hand. Our agent stopped first at signup: the Squarespace account form left Continue disabled with no error, blocked by an invisible reCAPTCHA Enterprise check, and no API route exists to sign up instead. It never reached verification, a key page or a call: robots.txt disallows the entire documented API base, closing that door too. No capability was driven. Pricing shows a no-card trial, but picking or leaving a plan happens in the web app after a person signs up.
Driven 11 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
A person has to set it up: L1 · Needs a person. Our agent read the docs headlessly without trouble, then stopped at sign-up, where a visible reCAPTCHA checkbox follows the sign-up form before any verification mail goes out. Without an account there was no personal access token, no OAuth consent and no completed MCP connection, so the API and the hosted MCP server both answered unauthorized and no scheduling action ran. Pricing stayed out of reach too: the billing page sits behind the same login, so our agent never saw checkout, upgrade or cancel, and no account existed to delete.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
Acuity SchedulingStopped at sign up: blocked
CalendlyStopped at sign up: needs a human
| Checkpoint | Acuity Scheduling | Calendly |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Needs a human |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Acuity Scheduling | Calendly | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | No | Yes (official) |
| CLI | No | No |
| SDK | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Acuity Scheduling | Calendly | |
|---|---|---|
| Bot check | reCAPTCHA Enterprise (invisible) on Squarespace login stopped it at sign up, without a visible challenge | reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A challenge on the form |
| First wall | Invisible reCAPTCHA stalls the Squarespace sign-up form | reCAPTCHA on the sign-up form |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Acuity Scheduling | Calendly | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 85 of 100, fair | 90 of 100, good |
| Standards | OpenAPI 3.1.0 (1 version behind) | MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Acuity Scheduling | Calendly | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Acuity Scheduling: Payment not reached.
- Calendly: Payment not reached.
Acuity Scheduling vs Calendly: the short answers.
Which can an AI agent use, Acuity Scheduling or Calendly?
Both reach L1 · Needs a person, and our agent got as far with each: with Acuity Scheduling it was stopped at sign up (blocked), with Calendly it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Acuity Scheduling) and 6 Oct 2026 (Calendly).
Can an AI agent sign up for Acuity Scheduling and Calendly on its own?
Acuity Scheduling: no, blocked. Calendly: no, needs a human.
Do Acuity Scheduling and Calendly have an MCP server?
Acuity Scheduling: none found. Calendly: yes (official).
Can an AI agent delete its Acuity Scheduling or Calendly account?
Acuity Scheduling: not reached. Calendly: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.