Acuity Scheduling vs TidyCal for AI agents
As of 12 Oct 2026, TidyCal gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- 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: Signs up in a browser.
- Use: 60% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Got in, in a browser; the API is paid. Next: do 80% of the core work (now 60%)
Does the work (L3): our agent got in on its own past an invisible reCAPTCHA on the sign-up form, no verification mail needed. It read the headless API docs and llms.txt, then stopped at credentials: API tokens and the MCP server need a paid plan, so GET /me came back unauthenticated. Inside the browser it still created a booking type and published it live on the public page. No agent payment rail exists; upgrading means a hosted Stripe card checkout, so our agent paid nothing and stayed on the free plan. Deleting the account worked cleanly through an emailed erasure link, with login and the booking page both gone after.
Gets furtherDriven 12 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
TidyCalGot in, in a browser; the API is paid
| Checkpoint | Acuity Scheduling | TidyCal |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | In a browser |
| Verify | Not reached | Not needed |
| Key | Not reached | Blocked |
| First call | Not reached | Blocked |
| First action | Not reached | In a browser |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | In a browser |
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 | TidyCal | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 4 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 2 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 60% of the core |
| 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 | TidyCal | |
|---|---|---|
| Bot check | reCAPTCHA Enterprise (invisible) on Squarespace login stopped it at sign up, without a visible challenge | Google reCAPTCHA (invisible) let it through at sign up |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Invisible reCAPTCHA stalls the Squarespace sign-up form | Got in, in a browser; the API is paid |
| 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. Where we drive from.
Level and part scores.
| Acuity Scheduling | TidyCal | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| 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.0.0 (2 versions 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 | TidyCal | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Acuity Scheduling: Payment not reached.
- TidyCal: Reaches the checkout: stopped at the card form.
Acuity Scheduling vs TidyCal: the short answers.
Which can an AI agent use, Acuity Scheduling or TidyCal?
TidyCal gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Acuity Scheduling our agent was stopped at sign up (blocked); with TidyCal it got in, in a browser (the API is paid). Driven 11 Oct 2026 (Acuity Scheduling) and 12 Oct 2026 (TidyCal).
Can an AI agent sign up for Acuity Scheduling and TidyCal on its own?
Acuity Scheduling: no, blocked. TidyCal: yes, in a browser.
Do Acuity Scheduling and TidyCal have an MCP server?
Acuity Scheduling: none found. TidyCal: yes (official).
Can an AI agent delete its Acuity Scheduling or TidyCal account?
Acuity Scheduling: not reached. TidyCal: yes, in a browser.
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.