# Calendly: L1 · Needs a person As of 6 Oct 2026, an AI agent can't use Calendly on its own: reCAPTCHA on the sign-up form. Source: https://agentdrives.com/tools/calendly?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 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. _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: Stopped by a CAPTCHA on the sign-up form. - Signed agents: The sign-up page opens. The CAPTCHA on the form stops them too. - 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: developer.calendly.com/llms.txt, Markdown pages (.md and Accept: text/markdown), OpenAPI 3.1.0 YAML with 65 operations, api-catalog linkset, and a docs-search MCP server, all fetched headless. - **Sign up**: Needs a human: Web form only (email, name, 12+ character password, terms). Submitting it shows a visible reCAPTCHA v2 'I'm not a robot' checkbox. - **Verify**: Not reached: Not reached: the sign-up stopped at the reCAPTCHA before any verification mail was due. - **Key**: Not reached: Personal access tokens are made in the web app after login; OAuth and the MCP server use DCR plus a browser consent page for a signed-in user. No device flow, no CIMD, no agent registration. All need an account. - **First call**: Not reached: No credentials: api.calendly.com and mcp.calendly.com answer 401. - **First action**: Not reached: No credentials. - **Pay**: Not reached: No 402 anywhere, no x402/MPP/UCP, no Bazaar or mpp.dev listing, no billing API. The pricing FAQ says upgrades happen on the billing page in the account; the checkout itself was not seen because creating the account needs a human (reCAPTCHA). Free plan plus a 14-day Teams trial without a card. - **Cancel**: Not reached: No plan was started. Help centre: cancel by switching to Free on the billing page (web UI); no billing API. - **Delete**: Not reached: No account was created. The API has no account delete operation; only Enterprise data-compliance deletion of invitee and event data. ## Does Calendly have an MCP server, and can an agent connect to it? Yes. Calendly has an official MCP server. 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 11 attempts worked. ## How does an AI agent get a Calendly API key? Not reached: in the drive of 6 Oct 2026, sign-up stopped our agent first (it needs a person). Personal access tokens are made in the web app after login; OAuth and the MCP server use DCR plus a browser consent page for a signed-in user. No device flow, no CIMD, no agent registration. All need an account. ## Paying the agent way Payment not reached. No card needed to start. 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 - Read the full API docs, OpenAPI and MCP setup guide without an account - Search the developer docs through the docs MCP server ## What it cannot do - Create a Calendly account: Visible reCAPTCHA v2 after the sign-up form - Get an API token or connect the MCP server: Every credential route needs a signed-in account - Any scheduling action (event types, bookings, availability, cancellations): No credentials ## Tips for the owner 1. Let verified agents sign up without reCAPTCHA 2. Offer a headless token path for new accounts 3. Support MCP (the 28 Jul 2026 spec) server/discover 4. Add a billing API or agent payment rail 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 · [Calendly vs TidyCal](https://agentdrives.com/compare/calendly-vs-tidycal?via=md) - [Acuity Scheduling](https://agentdrives.com/tools/acuityscheduling.md?via=md): L1 · Needs a person · [Calendly vs Acuity Scheduling](https://agentdrives.com/compare/acuityscheduling-vs-calendly?via=md) - [Cal.com](https://agentdrives.com/tools/cal.md?via=md): L1 · Needs a person · [Calendly vs Cal.com](https://agentdrives.com/compare/cal-vs-calendly?via=md) - [SavvyCal](https://agentdrives.com/tools/savvycal.md?via=md): L1 · Needs a person · [Calendly vs SavvyCal](https://agentdrives.com/compare/calendly-vs-savvycal?via=md) - [zcal](https://agentdrives.com/tools/zcal.md?via=md): L0 · Read-only ## Tips for agent builders - Use the MCP server at https://mcp.calendly.com once a human has an account: OAuth with DCR needs an https redirect URI (http loopback is refused). - Docs: append .md to any developer.calendly.com page; OpenAPI YAML at /openapi/calendly-api.yaml (the .json URL serves HTML). - Booking through the API (POST /invitees) needs a Standard plan or above; free accounts get the booking page only.