Calendly 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: 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 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.
CalendlyStopped at sign up: needs a human
TidyCalGot in, in a browser; the API is paid
| Checkpoint | Calendly | TidyCal |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | 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
| Calendly | TidyCal | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 4 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 2 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 60% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Calendly | TidyCal | |
|---|---|---|
| Bot check | reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge | Google reCAPTCHA (invisible) let it through at sign up |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | reCAPTCHA on the sign-up form | Got in, in a browser; the API is paid |
| A person helped | No | No |
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.
| Calendly | TidyCal | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Agent-ready setup | 90 of 100, good | 90 of 100, good |
| Standards | MCP client registration (behind) · 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.
| Calendly | 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
- Calendly: Payment not reached.
- TidyCal: Reaches the checkout: stopped at the card form.
Calendly vs TidyCal: the short answers.
Which can an AI agent use, Calendly or TidyCal?
TidyCal gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Calendly our agent was stopped at sign up (needs a human); with TidyCal it got in, in a browser (the API is paid). Driven 6 Oct 2026 (Calendly) and 12 Oct 2026 (TidyCal).
Can an AI agent sign up for Calendly and TidyCal on its own?
Calendly: no, needs a human. TidyCal: yes, in a browser.
Do Calendly and TidyCal have an MCP server?
Calendly: yes (official). TidyCal: yes (official).
Can an AI agent delete its Calendly or TidyCal account?
Calendly: 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.