Cal.com 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
Needs a person to start: L1 · Needs a person. Our agent read the headless docs fine, including a large OpenAPI and an MCP server card, but stopped at signup: the web form shows a Cloudflare Turnstile that stayed visible and never cleared for our agent's browser, so Get started stayed disabled. MCP client registration worked on its own, but authorization then redirects to a sign-in and consent page, and API keys are made in web settings, so no credentials followed either way. With no account, our agent never made a booking call and never reached checkout. There's also no API path to delete an account or the MCP client it registered.
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.
Cal.comStopped at sign up: needs a human
TidyCalGot in, in a browser; the API is paid
| Checkpoint | Cal.com | 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
| Cal.com | 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 | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Cal.com | TidyCal | |
|---|---|---|
| Bot check | Cloudflare Turnstile stopped it at sign up, with 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 | Cloudflare Turnstile on the 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.
| Cal.com | TidyCal | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Agent-ready setup | 100 of 100, good | 90 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 3.0.0 (2 versions 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.
| Cal.com | TidyCal | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Cal.com: Payment not reached.
- TidyCal: Reaches the checkout: stopped at the card form.
Cal.com vs TidyCal: the short answers.
Which can an AI agent use, Cal.com or TidyCal?
TidyCal gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Cal.com 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 (Cal.com) and 12 Oct 2026 (TidyCal).
Can an AI agent sign up for Cal.com and TidyCal on its own?
Cal.com: no, needs a human. TidyCal: yes, in a browser.
Do Cal.com and TidyCal have an MCP server?
Cal.com: yes (official). TidyCal: yes (official).
Can an AI agent delete its Cal.com or TidyCal account?
Cal.com: 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.