# Cal.com: L1 · Needs a person As of 6 Oct 2026, an AI agent can't use Cal.com on its own: Cloudflare Turnstile on the sign-up form. Source: https://agentdrives.com/tools/cal?via=md · driven 6 Oct 2026 by AgentDrives's agent · Same level in 3 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 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. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level. - 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 - Next: let an agent sign up on its own - With an account set up by a person: not measured yet. ## Level history - 1 Oct 2026 (2 drives): L1 · Needs a person - 6 Oct 2026: L1 · Needs a person ## Part scores - Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI not found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Turned away when they send the sign-up form. - Signed agents: The sign-up page opens. The check on the form still applies. - Agents in a person's browser: Not measured yet. Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: llms.txt, docs llms.txt with .md pages, OpenAPI 3.0.0 (235 paths, 356 operations), auth.md, agent-skills index, api-catalog, AI catalog: all fetched headless. - **Sign up**: Needs a human: No sign-up API (auth.md: no agent self-registration). Web form at app.cal.com/signup shows a visible Cloudflare Turnstile 'Verify you are human' that did not clear for our agent's browser; Get started stayed disabled. - **Verify**: Not reached: Not reached: no account created. - **Key**: Not reached: MCP DCR registration works headless (201 client_id), but authorization redirects to app.cal.com sign-in/consent and API keys are made in web settings; both need an account. No device flow or CIMD. - **First call**: Not reached: Unauthenticated calls answer 401/403 with clear JSON errors; no credentials to go further. MCP server/discover answers 401 Bearer token required. - **First action**: Not reached: No credentials. - **Pay**: Not reached: No 402 anywhere, x402./mpp./agents. subdomains do not resolve, no x-payment-info, not listed in x402 Bazaar or mpp.dev. No plan billing in the API (only credits and Stripe Connect for booking payments). Paid plans ($12/$28 per user/month, 14 day free trial) are bought in the web app after a sign-up a human must pass; checkout not observed, card requirement for the trial unknown. - **Cancel**: Not reached: No plan was started. - **Delete**: Not reached: No account to delete; the OpenAPI has no DELETE /v2/me, so deletion is not an API call. The MCP DCR client registration we created could not be deleted (no client delete endpoint is advertised). ## Does Cal.com have an MCP server, and can an agent connect to it? Yes. Cal.com has an official MCP server. The server is hosted and signs an agent in with OAuth. A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked. ## How does an AI agent get a Cal.com API key? Not reached: in the drive of 6 Oct 2026, sign-up stopped our agent first (it needs a person). MCP DCR registration works headless (201 client_id), but authorization redirects to app.cal.com sign-in/consent and API keys are made in web settings; both need an account. No device flow or CIMD. ## Paying the agent way Payment not reached. It has a free plan. What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. - List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev). From the drive of 6 Oct 2026. ## What an agent can do - Discover the API, MCP server, OAuth metadata and agent skills from well-known files without an account - Register an OAuth client on the MCP server headless (DCR) ## What it cannot do - Create a Cal.com account: Cloudflare Turnstile on the sign-up form did not clear for our agent's browser; no API sign-up - Get an API key or MCP token: Both need a signed-in Cal.com user - Any core scheduling task (event types, availability, bookings): No credentials - Delete the account headless: No DELETE /v2/me in the OpenAPI ## Tips for the owner 1. Let signed agents pass the sign-up Turnstile 2. Offer a headless agent sign-up or claim 3. Fix the API protected-resource link 4. Support MCP (the 28 Jul 2026 spec) discovery and CIMD 5. Add an account delete endpoint Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in Scheduling - [TidyCal](https://agentdrives.com/tools/tidycal.md?via=md): L3 · Does the work · [Cal.com vs TidyCal](https://agentdrives.com/compare/cal-vs-tidycal?via=md) - [Acuity Scheduling](https://agentdrives.com/tools/acuityscheduling.md?via=md): L1 · Needs a person · [Cal.com vs Acuity Scheduling](https://agentdrives.com/compare/acuityscheduling-vs-cal?via=md) - [Calendly](https://agentdrives.com/tools/calendly.md?via=md): L1 · Needs a person · [Cal.com vs Calendly](https://agentdrives.com/compare/cal-vs-calendly?via=md) - [SavvyCal](https://agentdrives.com/tools/savvycal.md?via=md): L1 · Needs a person · [Cal.com vs SavvyCal](https://agentdrives.com/compare/cal-vs-savvycal?via=md) - [zcal](https://agentdrives.com/tools/zcal.md?via=md): L0 · Read-only ## Tips for agent builders - Start at https://cal.com/auth.md and https://cal.com/.well-known/api-catalog: they list every machine-readable entry point. - Every API v2 call needs a cal-api-version header whose value is per-endpoint in openapi.json. - Get the human to create the account and an API key at app.cal.com/settings/developer/api-keys; sign-up has a Turnstile an agent cannot pass. - Use https://cal.com/.well-known/oauth-protected-resource, not the api.cal.com one (410). - Docs pages are available as markdown: append .md or send Accept: text/markdown.