Cal.com vs SavvyCal for AI agents
As of 6 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human).
- 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: 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.
Cal.comStopped at sign up: needs a human
SavvyCalStopped at sign up: needs a human
| Checkpoint | Cal.com | SavvyCal |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | 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
| Cal.com | SavvyCal | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | No |
| CLI | No | No |
| SDK | Yes | No |
| llms.txt | Yes | No |
Bot checks, and where a person was needed.
| Cal.com | SavvyCal | |
|---|---|---|
| Bot check | Cloudflare Turnstile stopped it at sign up, with 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 | Cloudflare Turnstile on the 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.
| Cal.com | SavvyCal | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 100 of 100, good | 30 of 100, poor |
| Standards | MCP client registration (behind) · OpenAPI 3.0.0 (2 versions 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.
| Cal.com | SavvyCal | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Cal.com: Payment not reached.
- SavvyCal: Payment not reached.
Cal.com vs SavvyCal: the short answers.
Which can an AI agent use, Cal.com or SavvyCal?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human). Both driven 6 Oct 2026.
Can an AI agent sign up for Cal.com and SavvyCal on its own?
Cal.com: no, needs a human. SavvyCal: no, needs a human.
Do Cal.com and SavvyCal have an MCP server?
Cal.com: yes (official). SavvyCal: none found.
Can an AI agent delete its Cal.com or SavvyCal account?
Cal.com: 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.