# TidyCal: L3 · Does the work As of 12 Oct 2026, an AI agent gets into TidyCal on its own, in a browser (the API key is paid), and does 60% of the core work. Source: https://agentdrives.com/tools/tidycal?via=md · driven 12 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 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. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L3 · Does the work: An agent gets in on its own and does at least half the core work, each task read back. - 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) - Ways in: Sign-up in a browser, 6 of 10 core tasks - Next: do 80% of the core work (now 60%) ## Level history - 2 Oct 2026: L1 · Needs a person - 6 Oct 2026: L3 · Does the work (sign-up varies) - 12 Oct 2026: L3 · Does the work ## 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: Get in on their own. - Signed agents: The sign-up page opens. - Agents in a person's browser: Not measured yet. Sign-up page checked 13 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: API reference at /developer/docs/ (Redoc, OpenAPI 3.0.0 embedded and downloadable, 16 operations), /llms.txt, /mcp-docs; all fetched headless. - **Sign up**: In a browser: Only route is the web form /register with invisible reCAPTCHA; no sign-up API or agent registration. Done in the browser with the agent's inbox; the check let our agent's browser through. - **Verify**: Not needed: No email verification: sign-up went straight to onboarding and the dashboard; no verification mail was sent. - **Key**: Blocked: API tokens and the MCP server are paid-only. Integrations > API on Free: 'Unlock Integrations by upgrading'. MCP OAuth: DCR registered a client headless, but /oauth/authorize on Free answered 'For API access please upgrade to a lifetime plan!'. - **First call**: Blocked: GET /api/me without a token: 401 {"message":"Unauthenticated."}; no token is obtainable on the free plan. - **First action**: In a browser: Created a booking type in the web app (Dashboard > Booking types > New booking type); it went live on the public page at once. - **Pay**: In a browser: No agent rail: no 402 on any TidyCal host, not in mpp.dev, Stripe Projects or the x402 Bazaar, no /.well-known/ucp, no billing API. We paid nothing. Pro is a live Stripe Checkout session (EUR 11.16/month, 'Billed monthly') reached from the pricing page while logged in; lifetime plans are sold on appsumo.com. Not paid: no card for this drive. - **Cancel**: Not needed: Nothing to cancel: our agent used the free plan. - **Delete**: In a browser: Settings > Account > Delete account emails a 'Data erasure request' link; opening it deleted the account ('Your account has been successfully deleted'). Login afterwards: 'These credentials do not match our records.'; the booking page /an inbox returns 404. No API route. ## Does TidyCal have an MCP server, and can an agent connect to it? Yes. TidyCal has an official MCP server. The server signs an agent in with OAuth. A new agent can get in on its own, in a browser: in the drive of 12 Oct 2026, our agent signed up and did its work in the web app without a person. API keys need a paid plan, so it got none. Through the MCP server, 0 of our agent's 2 attempts worked. ## How does an AI agent get a TidyCal API key? In the drive of 12 Oct 2026, our agent was blocked at this step and got no key. API tokens and the MCP server are paid-only. Integrations > API on Free: 'Unlock Integrations by upgrading'. MCP OAuth: DCR registered a client headless, but /oauth/authorize on Free answered 'For API access please upgrade to a lifetime plan!'. ## Paying the agent way Reaches the checkout: stopped at the card form. 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). Ways to pay checked 12 Oct 2026. ## What an agent can do - Create, edit and delete a booking type in the web app, live at once on the public booking page - Set buffer time, minimum notice and how far ahead bookings can be made - Book, reschedule and cancel an appointment as an attendee on the public page - Create a coupon code - Get the review link and list contacts - Delete the account through the web app and an emailed link ## What it cannot do - Use the REST API or MCP server: Paid plans only; on Free no token can be made and OAuth authorize refuses - Sign up headless: Only a web form with reCAPTCHA; no sign-up API - Take paid bookings, subscriptions, packages or sell products: Needs a Stripe or PayPal merchant account connected - Sync a calendar: Needs a Google, Microsoft or Apple calendar account - Run a date poll: Not found: no menu entry and /date-polls is 404 - Buy Pro without a person's card: Only a hosted Stripe Checkout; no agent payment rail or billing API ## Tips for the owner 1. Open read-only API access on Free 2. Make MCP authorize match its docs 3. Add a documented agent sign-up route 4. Fix the pricing Subscribe link 5. Accept an agent payment rail for Pro 6. Support CIMD next to DCR 7. Add securitySchemes and serve the OpenAPI file 8. Add an account delete API call 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 - [Acuity Scheduling](https://agentdrives.com/tools/acuityscheduling.md?via=md): L1 · Needs a person · [TidyCal vs Acuity Scheduling](https://agentdrives.com/compare/acuityscheduling-vs-tidycal?via=md) - [Cal.com](https://agentdrives.com/tools/cal.md?via=md): L1 · Needs a person · [TidyCal vs Cal.com](https://agentdrives.com/compare/cal-vs-tidycal?via=md) - [Calendly](https://agentdrives.com/tools/calendly.md?via=md): L1 · Needs a person · [TidyCal vs Calendly](https://agentdrives.com/compare/calendly-vs-tidycal?via=md) - [SavvyCal](https://agentdrives.com/tools/savvycal.md?via=md): L1 · Needs a person · [TidyCal vs SavvyCal](https://agentdrives.com/compare/savvycal-vs-tidycal?via=md) - [zcal](https://agentdrives.com/tools/zcal.md?via=md): L0 · Read-only ## Tips for agent builders - On Free, everything is in the web app: drive it in a browser; the API and MCP need Pro or a lifetime plan. - Booking type forms need title, URL slug and description in one go; a missing description gives 'The description field is required.' - The public booking page has a second email field (the footer sign-up); target the one inside the booking dialog. - Confirmation mails carry reschedule and cancel links with a booker_token; use them to change a booking as the attendee. - Account delete needs the emailed confirmation link.