Acuity Scheduling vs SavvyCal 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 SavvyCal 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: No docs for agents.
- 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 get this one started: L1 · Needs a person. Our agent stopped at the sign-up form itself, where a visible hCaptcha image puzzle appears on page load, before it could reach verification, a token, or any endpoint. Documentation covers events, scheduling links, the current user, time zones, webhooks and workflows, with PAT and OAuth auth, but every call without a token returns an unauthenticated response, so none of that surface got exercised. Plans are bought on the web billing page, reachable only after a human clears sign-up, and both cancelling and deleting an account stay web-only with no API route either way.
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
SavvyCalStopped at sign up: needs a human
| Checkpoint | Acuity Scheduling | SavvyCal |
|---|---|---|
| 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 | SavvyCal | |
|---|---|---|
| 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 | No |
| MCP server | No | No |
| CLI | No | No |
| SDK | Yes | No |
| llms.txt | Yes | No |
Bot checks, and where a person was needed.
| Acuity Scheduling | SavvyCal | |
|---|---|---|
| Bot check | reCAPTCHA Enterprise (invisible) on Squarespace login stopped it at sign up, without a visible challenge | hCaptcha (image puzzle) 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 | hCaptcha puzzle 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 | SavvyCal | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 85 of 100, fair | 30 of 100, poor |
| Standards | OpenAPI 3.1.0 (1 version behind) | MCP client registration (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 | SavvyCal | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Acuity Scheduling: Payment not reached.
- SavvyCal: Payment not reached.
Acuity Scheduling vs SavvyCal: the short answers.
Which can an AI agent use, Acuity Scheduling or SavvyCal?
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 SavvyCal it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Acuity Scheduling) and 6 Oct 2026 (SavvyCal).
Can an AI agent sign up for Acuity Scheduling and SavvyCal on its own?
Acuity Scheduling: no, blocked. SavvyCal: no, needs a human.
Do Acuity Scheduling and SavvyCal have an MCP server?
Acuity Scheduling: none found. SavvyCal: none found.
Can an AI agent delete its Acuity Scheduling or SavvyCal account?
Acuity Scheduling: not reached. SavvyCal: 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.