{ "data": { "a": { "slug": "calendly", "name": "Calendly API + MCP", "vendor": "Calendly", "vendorUrl": "https://calendly.com", "kind": "http-api", "category": "scheduling", "summary": "Calendly's scheduling API for availability, bookings, invitees and webhooks, with a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/calendly", "markdownUrl": "https://www.anchorterminal.com/tools/calendly.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/calendly.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/calendly.json", "dns": "calendly.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.calendly.com", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens for your own account, OAuth apps for other people's. Both go in the `Authorization: Bearer` header. The hosted MCP uses OAuth 2.1 with PKCE and dynamic client registration only. Only 8 OAuth tokens per user can be requested in a minute.", "pricing": "freemium", "pricingNotes": "Free plan. The pricing page lists Standard at $10 a seat a month and Teams at $16, and says yearly billing saves 17 and 20 per cent. Enterprise starts at $15,000 a year with a 50-seat minimum, in USD only (https://calendly.com/pricing). Booking through the API needs Standard or above (https://developer.calendly.com/api-docs/calendly-api/scheduled-events/create-event-invitee.md).", "priceSummary": "$10 / seat-mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 39, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developer.calendly.com", "llmsTxt": "https://developer.calendly.com/llms.txt", "openapi": "https://developer.calendly.com/openapi/calendly-api.json", "capabilities": [ "calendar.read", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "mcp", "llms-txt", "openapi", "webhooks", "oauth", "closed-source", "enterprise" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 69.1, "grade": "B", "agentReady": false, "rank": 236, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 60, "payments": 30, "reliability": 85, "schema": 86, "security": 70, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.", "bestFor": "Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.", "strengths": [ "Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP", "MCP tools annotated with readOnlyHint, destructiveHint and idempotentHint", "OpenAPI 3.1 in JSON and YAML, llms.txt and Markdown copies of every page", "Status page with separate API and Webhooks components, both at 100% uptime, and no incident in its feed on 1 November 2026", "SOC 2 Type 2 and ISO 27001, with an activity log scope on Enterprise" ], "weaknesses": [ "Booking through the API needs a paid seat, and Free users get a 403", "Booking limited to 10 a minute, 50 an hour and 100 a day per user below Enterprise", "No idempotency key on POST /invitees", "No official SDK", "Tokens issued before scoped permissions keep full access" ], "agentNotes": [ "Resolve the user's URI with GET /users/me before listing event types or busy times", "Pass `start_time` in UTC and the invitee's `timezone` when calling POST /invitees", "List the invitee's scheduled events before retrying a booking, since there's no idempotency key", "Read `X-RateLimit-Reset` on 429 and wait that many seconds", "Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.1 } ], "editorialScores": { "ergonomics": 61, "maintenance": 60, "payments": 30, "reliability": 85, "schema": 86, "security": 70, "transparency": 61 }, "provenanceScore": 99, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.calendly.com/users/me -H \"Authorization: Bearer $CALENDLY_TOKEN\"", "claudeCode": "claude mcp add --transport http calendly https://mcp.calendly.com", "config": { "mcpServers": { "calendly": { "url": "https://mcp.calendly.com" } } } }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/calendly" }, "area": "everyday", "unitPrices": [ { "item": "Standard", "unit": "seat-month", "usd": 10, "note": "Headline price on the pricing page, which toggles yearly and monthly billing" }, { "item": "Teams", "unit": "seat-month", "usd": 16, "note": "Headline price on the pricing page, which toggles yearly and monthly billing" } ], "provenance": { "legalEntity": "Calendly, LLC", "domain": "calendly.com", "domainRegistered": "2013-02-26", "endpointOnVendorDomain": true, "terms": "https://calendly.com/legal/customer-terms-conditions", "privacy": "https://calendly.com/legal/privacy-notice", "statusPage": "https://www.calendlystatus.com", "changelog": "https://developer.calendly.com/release-notes", "securityTxt": "valid", "checked": "2026-09-30", "notes": [ "The privacy notice (updated 3 July 2026) names Calendly, LLC and a postal address in Buford, Georgia, and lists EEA and UK representatives.", "security.txt lists security@calendly.com and expires 2027-04-10.", "A developer policy sits at calendly.com/legal/developer-policy alongside the customer terms." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/calendly.json", "live": { "slug": "calendly", "probe": { "target": "https://api.calendly.com", "method": "get", "lastAt": "2026-11-04T21:39:17.703365304Z", "lastOk": true, "lastStatus": 401, "lastMs": 128, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 139, "p95ms24h": 231, "samples24h": 247, "samples30d": 8090, "days": [ { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 223, "ok": 223 } ] }, "vendorStatus": { "page": "https://www.calendlystatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:37:48.404507018Z" }, "securityTxt": { "url": "https://calendly.com/.well-known/security.txt", "state": "valid", "expires": "2027-04-10T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:17.797160523Z" }, "llmsTxt": { "url": "https://developer.calendly.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:22:16.04503322Z" }, "domain": { "domain": "calendly.com", "registered": "2013-02-26", "source": "https://rdap.verisign.com/com/v1/domain/calendly.com", "checkedAt": "2026-11-01T14:15:29.552044032Z" }, "pages": [ { "url": "https://developer.calendly.com/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-04T08:18:08.058765972Z", "changedAt": "2026-10-31T06:07:16.765948381Z", "fingerprint": "858df4997394" }, { "url": "https://calendly.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:16:17.294315476Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d5a9d70a2911" }, { "url": "https://calendly.com/legal/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:16:15.286702441Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "881ce0a81fb2" }, { "url": "https://calendly.com/legal/customer-terms-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:16:12.854104272Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b8ae1bf79b38" } ], "updatedAt": "2026-11-04T21:39:17.703365304Z" } }, "answer": "Calendly API + MCP scores 69.1 (B) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 6 of 7 scored categories.", "b": { "slug": "youcanbookme", "name": "YouCanBookMe API", "vendor": "AI Software (Capacity) UK Ltd, trading as YouCanBookMe", "vendorUrl": "https://youcanbook.me", "kind": "http-api", "category": "scheduling", "summary": "YouCanBookMe is a booking-page service from the UK company of the same name, owned by Capacity since 2025. Its REST API manages account details, booking pages (profiles) and bookings over HTTP Basic auth, with webhooks from booking notifications.", "url": "https://www.anchorterminal.com/tools/youcanbookme", "markdownUrl": "https://www.anchorterminal.com/tools/youcanbookme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/youcanbookme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/youcanbookme.json", "dns": "youcanbookme.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.youcanbook.me/v1", "packages": [], "auth": "api-key", "authNotes": "HTTP Basic authentication with the account email address or account ID as the username and an account API key as the password. Only the Account Owner can generate, view, copy or delete the key, under Account Password \u0026 Security \u003e Authentication and API, and the help centre says the API key is available on the Team plan. No scopes, expiry or per-user keys are described. Administrators and Contributors must ask the owner for the key.", "pricing": "freemium", "pricingNotes": "Free plan with 1 calendar, 1 booking page and 30 bookings a month, with YouCanBookMe branding. Individual $9, Professional $13 and Teams $18 a seat a month, with 10 per cent off yearly and 20 per cent off for two years ($7.20, $10.40 and $14.40), per the help centre's pricing article. 14-day trial of every feature with no card, per the pricing page. API access is listed under the Team plan; webhooks need Professional or Teams.", "priceSummary": "$9 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, in the help centre API and webhook articles or in the API's error response (checked 2026-11-03). The API reference itself could not be read.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://ycbm.stoplight.io/", "capabilities": [ "calendar.booking", "calendar.availability", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "free-trial", "no-card", "api-key", "webhooks", "soc2", "iso27001", "uk", "closed-source" ], "lastRelease": "2026-09-01", "graded": true, "anchor": { "graded": true, "score": 22.5, "grade": "F", "agentReady": false, "rank": 1287, "ranked": true, "rankOf": 1349, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 13, "maintenance": 28, "payments": 30, "reliability": 15, "schema": 10, "security": 24, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "A booking-page service with a Team-plan REST API over HTTP Basic auth and one account-wide key, SOC 2 Type II and ISO 27001 on its security page, and a 14-day trial without a card. Its API reference renders only by JavaScript and its status page did not resolve for us, so endpoints, limits and incidents are unverified.", "bestFor": "A booking-page product for small businesses, closest to calendly and savvycal in scheduling.", "strengths": [ "SOC 2 Type II and ISO/IEC 27001:2022 (certificate issued 20 February 2024) listed on the security page, with AES-256 at rest on AWS", "Free plan and a 14-day trial of every feature with no card", "Privacy notice (16 March 2026) states retention periods, 24 months for booking data by default, and says booking data is not used to train AI models", "Webhook notifications on six booking triggers with a JSON payload the user shapes, on Professional and Teams", "The API answers with a JSON error envelope carrying a code, message and status, and declares its version in an `x-api-version` header" ], "weaknesses": [ "The API reference at ycbm.stoplight.io could not be read without JavaScript, and the help centre's API article sat behind a Cloudflare challenge", "One account-wide API key over HTTP Basic auth, created only by the Account Owner, with no scopes or expiry documented", "API access is listed only on the Team plan ($18 a seat a month)", "No rate limits, 429 handling, idempotency keys, OpenAPI file, llms.txt or official SDK were found", "No security.txt, bug bounty or disclosure policy, and the status page at youcanbookmestatus.com did not resolve for us" ], "agentNotes": [ "Ask the Account Owner for the account ID and API key, since Administrators and Contributors cannot generate one, and send them as HTTP Basic credentials", "Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us", "Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented", "Expect a JSON error body with `code`, `message` and `status` on failures, and check for an existing booking before repeating a create, since no idempotency key is documented", "Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 22.5 } ], "editorialScores": { "ergonomics": 13, "maintenance": 28, "payments": 30, "reliability": 15, "schema": 10, "security": 24, "transparency": 52 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -u \"$YCBM_ACCOUNT_ID:$YCBM_API_KEY\" https://api.youcanbook.me/v1/profiles" }, "letme": { "capability": "https://letme.dev/calendar.booking", "tool": "https://letme.dev/youcanbookme" }, "area": "everyday", "unitPrices": [ { "item": "Individual", "unit": "seat-month", "usd": 9, "note": "$8.10 a month yearly, $7.20 over two years, per the help centre" }, { "item": "Professional", "unit": "seat-month", "usd": 13, "note": "$11.70 a month yearly, $10.40 over two years" }, { "item": "Teams", "unit": "seat-month", "usd": 18, "note": "Per seat. $16.20 yearly, $14.40 over two years. The plan that lists API access" } ], "provenance": { "legalEntity": "AI Software (Capacity) UK Ltd", "domain": "youcanbook.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://youcanbook.me/terms", "privacy": "https://youcanbook.me/privacy", "statusPage": "https://www.youcanbookmestatus.com", "changelog": "https://youcanbook.me/product-updates", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms (last updated 18 March 2026) name AI Software (Capacity) UK Ltd, trading as YouCanBookMe, under English law. Clause 15.3 bars data mining, robots and similar extraction tools without written consent, and clause 7.2 bars downloading the Site's software. Recorded as a fact; the public pages were read.", "The privacy notice (16 March 2026) gives company number 7221202, AWS hosting in the United States, a DPA on request through HelloSign, and retention of 24 months for booking data and up to 7 years for support messages.", "youcanbook.me/robots.txt disallows only HubSpot preview and preference paths. support.youcanbook.me/robots.txt disallows account, search and request paths; the API article there answered a Cloudflare challenge (403), which is the host's block, not a robots rule. ycbm.capacity.com and ycbm.stoplight.io allow all.", "The status page linked from youcanbook.me/help, www.youcanbookmestatus.com, did not resolve from our reader on 3 November 2026 (DNS), with or without www, so no incident history was read.", "youcanbook.me/.well-known/security.txt returns 404. The security page gives compliance@youcanbook.me as its contact.", "RDAP for youcanbook.me (rdap.nic.me) could not be reached from our shell, so the registration date is blank.", "The product updates page at youcanbook.me/product-updates is dated by month; its newest entry is September 2026 (registered SMS numbers), which lastRelease records as the first of that month." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/youcanbookme.json", "live": { "slug": "youcanbookme", "probe": { "target": "https://api.youcanbook.me/v1", "method": "get", "lastAt": "2026-11-04T21:39:54.948803292Z", "lastOk": true, "lastStatus": 400, "lastMs": 406, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 200, "p95ms24h": 447, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://www.youcanbookmestatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:27:01.611847667Z" }, "securityTxt": { "url": "https://youcanbook.me/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:28.156243558Z" }, "updatedAt": "2026-11-04T21:39:54.948803292Z" } }, "edges": [ { "by": 76, "category": "schema", "leads": "calendly", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 for the scheduling API and a separate one for OAuth, in JSON and YAML (25). llms.txt with about 130 links and Markdown copies of every docs page (10). Reference pages and MCP tool docs mark plan requirements such as paid plan for booking and Teams for routing forms (14). Typed parameters in the spec (12). 400, 401, 403, 404, 409, 424 and 500 responses in the spec. 429 appears on 9 of 65 operations, the contacts endpoints, on 1 November 2026 (12). Dated release notes, latest 30 October 2026. The API version only changes by migration, the last one being v1 to v2 (13).", "b": "The reference lives on Stoplight at ycbm.stoplight.io, which usually renders an OpenAPI file, but our reader got only the workspace shell, and no spec file was found at the usual paths; the help centre article on support.youcanbook.me sat behind a Cloudflare challenge. Scored absent (0 of 25). No llms.txt on youcanbook.me, the help centre or the Stoplight host (0). Descriptions, typed inputs and required fields unread (0 of 20, 0 of 15). The one response we saw is a JSON envelope with `code`, `errors`, `httpCode`, `message` and `status`, and the help centre gives a worked webhook payload (4 of 15). A /v1 path and `x-api-version: 1.18` and `x-api-revision` headers, with a product updates page dated by month and no API changelog (6 of 15). 0 + 0 + 0 + 0 + 4 + 6 = 10." }, "scores": { "a": 86, "b": 10 } }, { "by": 70, "category": "reliability", "leads": "calendly", "name": "Reliability", "reasons": { "a": "incident.io status page with separate Calendly API and Webhooks components, plus each calendar provider (20). The page shows 100% uptime for the API and Webhooks components from August to November 2026, and its RSS feed, read on 1 November 2026, lists one completed maintenance window (6 September) and no incidents, so a clean record (30). 500 requests a minute per user on paid plans, 50 on Free, and booking capped at 10 a minute, 50 an hour and 100 a day below Enterprise (15). 429 with X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice, but no idempotency key or safe-retry guidance for booking writes (10). No SLA found on any plan (0). API v2 is GA (10).", "b": "Read with the hosted lines. The help page links a status page at www.youcanbookmestatus.com, but the host did not resolve from our reader with or without www on 3 November 2026, so it is scored as not established rather than as a finding about the vendor (0). No readable history (5). No rate limit with a number in the help centre articles, the pricing page or the API's own error response; the API reference could not be read (0). No 429 or retry guidance and no idempotency key found (0). No SLA, and the terms say the service is not guaranteed to be available 100 per cent of the time (0). The API reports version 1.18 in its headers and is sold on the Team plan, so generally available (10). 0 + 5 + 0 + 0 + 0 + 10 = 15." }, "scores": { "a": 85, "b": 15 } }, { "by": 48, "category": "ergonomics", "leads": "calendly", "name": "Agent ergonomics", "reasons": { "a": "39 MCP tools on the supported tools page on 1 November 2026 (5), with 5 back for two skill tools that load task guidance on demand and 2 for `count` on REST lists (12). `next_page` pagination and time and status filters on scheduled events (17). Error codes in the spec, and Free users get a clear 403 on booking (15). MCP tools carry readOnlyHint, destructiveHint and idempotentHint, but the REST booking call has no idempotency key (12). No official SDK, and the user URI from /users/me is needed before most calls (5).", "b": "Response sizing, field selection and pagination are in the unread reference (3 of 25, 0 of 20). The error envelope names a machine code and a message an agent can branch on (8 of 20). No idempotency key or safe-retry guidance found (0 of 20). No official SDK, and the required parameters are unread (2 of 15). 3 + 0 + 8 + 0 + 2 = 13." }, "scores": { "a": 61, "b": 13 } }, { "by": 46, "category": "security", "leads": "calendly", "name": "Security \u0026 auth", "reasons": { "a": "OAuth 2.1 with PKCE and dynamic client registration on the MCP, and per-resource scopes such as `scheduled_events:read` and `availability:write` for new OAuth apps and new personal access tokens since March 2026. Tokens issued before scopes keep full access (28). Read scopes, `mcp:scheduling:read` and `mcp:scheduling:write` for the MCP, and destructiveHint on cancel, delete and revoke tools, but no confirmation step of its own (15). Invitee names and booking answers written by outsiders reach the model, with no injection guidance found (0). `activity_log:read` and audit logs on Enterprise (10). SOC 2 Type 2, ISO 27001, CSA STAR, an annual penetration test and a valid security.txt. No public bug bounty found (17).", "b": "One account-wide API key sent as the HTTP Basic password with the account ID or email, generated and deleted by the Account Owner only; no scopes, expiry or per-user keys are documented (10 of 30). No read-only mode or confirmation step found (0 of 20). The API and webhooks carry names, answers and notes written by people who book, with no injection guidance (2 of 15). No audit log or per-call visibility found (0 of 15). SOC 2 Type II and ISO/IEC 27001:2022 (certificate 20/3433, 20 February 2024) and third-party penetration tests on the security page, but no security.txt (404), bug bounty or disclosure policy (12 of 20). 10 + 0 + 2 + 0 + 12 = 24." }, "scores": { "a": 70, "b": 24 } }, { "by": 32, "category": "maintenance", "leads": "calendly", "name": "Maintenance \u0026 community", "reasons": { "a": "Latest release note on 30 October 2026 (Teams API), two days before this check (30). Four dated entries since 3 August (25 August, 22, 23 and 30 October) (20). Public release notes and a developer support route, no public issue tracker (10). No official SDKs (0). No package to assess (0).", "b": "Read as a closed service. The newest product update is dated September 2026 (registered SMS numbers), within 90 days but not 30, taking the month's first day (20 of 30). The previous entry is November 2025, so fewer than three in 90 days (0 of 20). A help centre, a community forum at forum.youcanbook.me and one-to-one support for paid users, with a product updates page that carries no API items (8 of 15). No official SDKs found (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28." }, "scores": { "a": 60, "b": 28 } }, { "by": 19, "category": "transparency", "leads": "calendly", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with customer terms and a separate developer policy (15). Privacy notice (3 July 2026) gives no retention periods, and the no-AI-training statement sits on the security page, not in the privacy notice (18). The v1 to v2 migration notice is dated 26 March 2025 and legacy token behaviour under scopes is written down (12). Sub-processor list linked from the privacy notice, which says data sits in the US or wherever providers operate. We didn't open the list (16).", "b": "Closed service with terms (18 March 2026) naming AI Software (Capacity) UK Ltd under English law, which bar data-mining and robot tools without consent and let the company end membership without notice for a breach (15 of 30). The privacy notice (16 March 2026) states retention periods (24 months for booking data by default, 7 years for support messages), AWS hosting in the United States, a DPA on request and no training of external AI models on booking data; the security page says no subprocessor list is published, and the two agree on AWS (22 of 30). No deprecation policy or dated notice, and clause 18.4 allows changes to the service without notice (3 of 20). Providers are named in the privacy notice (AWS, Stripe, Google Analytics, Mixpanel, Hotjar, HubSpot) with US hosting, but there is no list with locations per processor (12 of 20). 15 + 22 + 3 + 12 = 52." }, "scores": { "a": 80, "b": 61 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Calendly", "b": "AI Software (Capacity) UK Ltd, trading as YouCanBookMe", "name": "Vendor" }, { "a": "https://api.calendly.com", "b": "https://api.youcanbook.me/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "39", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-09-01", "name": "Last release" }, { "a": "2026-08-05", "b": "2026-03-18", "name": "Terms last updated" }, { "a": "2026-07-03", "b": "2026-03-16", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Calendly API + MCP scores 69.1 (B) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Calendly API + MCP or YouCanBookMe API?" }, { "answer": "Calendly API + MCP takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.", "question": "Do Calendly API + MCP and YouCanBookMe API need an API key?" }, { "answer": "Yes. Calendly API + MCP has a hosted endpoint at https://api.calendly.com and YouCanBookMe API at https://api.youcanbook.me/v1.", "question": "Can an agent call Calendly API + MCP and YouCanBookMe API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 15", "Schema \u0026 documentation, 86 against 10", "Agent ergonomics, 61 against 13", "Security \u0026 auth, 70 against 24", "Maintenance \u0026 community, 60 against 28", "Transparency \u0026 trust, 80 against 61" ], "also": null, "goodFor": "Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.", "slug": "calendly", "watchFor": "Booking through the API needs a paid seat, and Free users get a 403" }, { "aheadOn": null, "also": [ "Free to start without a card" ], "goodFor": "A booking-page product for small businesses, closest to calendly and savvycal in scheduling.", "slug": "youcanbookme", "watchFor": "The API reference at ycbm.stoplight.io could not be read without JavaScript, and the help centre's API article sat behind a Cloudflare challenge" } ], "history": { "calendly": [ { "causes": [ "product" ], "date": "2026-11-01", "delta": 0.8, "from": 68.3, "fromGrade": "B", "to": 69.1, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.1, "from": 68.4, "fromGrade": "B", "to": 68.3, "toGrade": "B" } ], "youcanbookme": null }, "job": { "capability": "calendar.booking", "name": "Calendar booking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly.json", "title": "Acuity Scheduling API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-calendly.json", "title": "Agenda Hero vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-calendly.json", "title": "Apiroc Unified Calendar API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/apiroc-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.json", "title": "Aurinko Calendar API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-calendly.json", "title": "Cal.com API v2 + MCP vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/cal-com-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-cozi.json", "title": "Calendly API + MCP vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/calendly-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-cronofy.json", "title": "Calendly API + MCP vs Cronofy API", "url": "https://www.anchorterminal.com/compare/calendly-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-google-calendar-api.json", "title": "Calendly API + MCP vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/calendly-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar.json", "title": "Calendly API + MCP vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.json", "title": "Calendly API + MCP vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-savvycal.json", "title": "Calendly API + MCP vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/calendly-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler.json", "title": "Calendly API + MCP vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.json", "title": "Acuity Scheduling API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.json", "title": "Aurinko Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.json", "title": "Cal.com API v2 + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.json", "title": "Cronofy API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.json", "title": "Nylas Calendar and Scheduler API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.json", "title": "SavvyCal API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.json", "title": "YouCanBookMe API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.json", "title": "Apiroc Unified Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.json", "title": "Google Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.json", "title": "Microsoft Graph Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme" } ], "panel": null, "scores": [ { "by": 70, "calendly": 85, "edge": "calendly", "key": "reliability", "name": "Reliability", "weight": 16, "youcanbookme": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 76, "calendly": 86, "edge": "calendly", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "youcanbookme": 10 }, { "by": 48, "calendly": 61, "edge": "calendly", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "youcanbookme": 13 }, { "by": 46, "calendly": 70, "edge": "calendly", "key": "security", "name": "Security \u0026 auth", "weight": 14, "youcanbookme": 24 }, { "by": 0, "calendly": 30, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "youcanbookme": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 32, "calendly": 60, "edge": "calendly", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "youcanbookme": 28 }, { "by": 19, "calendly": 80, "edge": "calendly", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "youcanbookme": 61 } ], "summary": "Calendly API + MCP scores 69.1 (B) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 6 of 7 scored categories. Both do calendar booking.", "tasks": null, "tutorials": [], "verdicts": { "calendly": "Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.", "youcanbookme": "A booking-page service with a Team-plan REST API over HTTP Basic auth and one account-wide key, SOC 2 Type II and ISO 27001 on its security page, and a 14-day trial without a card. Its API reference renders only by JavaScript and its status page did not resolve for us, so endpoints, limits and incidents are unverified." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme", "json": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.min.md" }, "markdown": "Calendly API + MCP scores 69.1 (B) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 6 of 7 scored categories. Both do calendar booking.\n\n- Calendly API + MCP: grade B, 69.1/100, rank #236 of 1349. Markdown https://www.anchorterminal.com/tools/calendly.md · JSON https://www.anchorterminal.com/api/v1/tools/calendly.json\n- YouCanBookMe API: grade F, 22.5/100, rank #1287 of 1349. Markdown https://www.anchorterminal.com/tools/youcanbookme.md · JSON https://www.anchorterminal.com/api/v1/tools/youcanbookme.json\n- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md\n- All 89 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md\n\n## Which one, for what\n\n### Calendly API + MCP (B)\n\nGood for: Best when the host already schedules through Calendly and the agent needs to find a slot and book or cancel it.\n\nAhead on:\n- Reliability, 85 against 15\n- Schema \u0026 documentation, 86 against 10\n- Agent ergonomics, 61 against 13\n- Security \u0026 auth, 70 against 24\n- Maintenance \u0026 community, 60 against 28\n- Transparency \u0026 trust, 80 against 61\n\nWatch for: Booking through the API needs a paid seat, and Free users get a 403\n\n### YouCanBookMe API (F)\n\nGood for: A booking-page product for small businesses, closest to calendly and savvycal in scheduling.\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The API reference at ycbm.stoplight.io could not be read without JavaScript, and the help centre's API article sat behind a Cloudflare challenge\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Calendly API + MCP +76\n\n- Calendly API + MCP (86): OpenAPI 3.1 for the scheduling API and a separate one for OAuth, in JSON and YAML (25). llms.txt with about 130 links and Markdown copies of every docs page (10). Reference pages and MCP tool docs mark plan requirements such as paid plan for booking and Teams for routing forms (14). Typed parameters in the spec (12). 400, 401, 403, 404, 409, 424 and 500 responses in the spec. 429 appears on 9 of 65 operations, the contacts endpoints, on 1 November 2026 (12). Dated release notes, latest 30 October 2026. The API version only changes by migration, the last one being v1 to v2 (13).\n- YouCanBookMe API (10): The reference lives on Stoplight at ycbm.stoplight.io, which usually renders an OpenAPI file, but our reader got only the workspace shell, and no spec file was found at the usual paths; the help centre article on support.youcanbook.me sat behind a Cloudflare challenge. Scored absent (0 of 25). No llms.txt on youcanbook.me, the help centre or the Stoplight host (0). Descriptions, typed inputs and required fields unread (0 of 20, 0 of 15). The one response we saw is a JSON envelope with `code`, `errors`, `httpCode`, `message` and `status`, and the help centre gives a worked webhook payload (4 of 15). A /v1 path and `x-api-version: 1.18` and `x-api-revision` headers, with a product updates page dated by month and no API changelog (6 of 15). 0 + 0 + 0 + 0 + 4 + 6 = 10.\n\n### Reliability: Calendly API + MCP +70\n\n- Calendly API + MCP (85): incident.io status page with separate Calendly API and Webhooks components, plus each calendar provider (20). The page shows 100% uptime for the API and Webhooks components from August to November 2026, and its RSS feed, read on 1 November 2026, lists one completed maintenance window (6 September) and no incidents, so a clean record (30). 500 requests a minute per user on paid plans, 50 on Free, and booking capped at 10 a minute, 50 an hour and 100 a day below Enterprise (15). 429 with X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice, but no idempotency key or safe-retry guidance for booking writes (10). No SLA found on any plan (0). API v2 is GA (10).\n- YouCanBookMe API (15): Read with the hosted lines. The help page links a status page at www.youcanbookmestatus.com, but the host did not resolve from our reader with or without www on 3 November 2026, so it is scored as not established rather than as a finding about the vendor (0). No readable history (5). No rate limit with a number in the help centre articles, the pricing page or the API's own error response; the API reference could not be read (0). No 429 or retry guidance and no idempotency key found (0). No SLA, and the terms say the service is not guaranteed to be available 100 per cent of the time (0). The API reports version 1.18 in its headers and is sold on the Team plan, so generally available (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.\n\n### Agent ergonomics: Calendly API + MCP +48\n\n- Calendly API + MCP (61): 39 MCP tools on the supported tools page on 1 November 2026 (5), with 5 back for two skill tools that load task guidance on demand and 2 for `count` on REST lists (12). `next_page` pagination and time and status filters on scheduled events (17). Error codes in the spec, and Free users get a clear 403 on booking (15). MCP tools carry readOnlyHint, destructiveHint and idempotentHint, but the REST booking call has no idempotency key (12). No official SDK, and the user URI from /users/me is needed before most calls (5).\n- YouCanBookMe API (13): Response sizing, field selection and pagination are in the unread reference (3 of 25, 0 of 20). The error envelope names a machine code and a message an agent can branch on (8 of 20). No idempotency key or safe-retry guidance found (0 of 20). No official SDK, and the required parameters are unread (2 of 15). 3 + 0 + 8 + 0 + 2 = 13.\n\n### Security \u0026 auth: Calendly API + MCP +46\n\n- Calendly API + MCP (70): OAuth 2.1 with PKCE and dynamic client registration on the MCP, and per-resource scopes such as `scheduled_events:read` and `availability:write` for new OAuth apps and new personal access tokens since March 2026. Tokens issued before scopes keep full access (28). Read scopes, `mcp:scheduling:read` and `mcp:scheduling:write` for the MCP, and destructiveHint on cancel, delete and revoke tools, but no confirmation step of its own (15). Invitee names and booking answers written by outsiders reach the model, with no injection guidance found (0). `activity_log:read` and audit logs on Enterprise (10). SOC 2 Type 2, ISO 27001, CSA STAR, an annual penetration test and a valid security.txt. No public bug bounty found (17).\n- YouCanBookMe API (24): One account-wide API key sent as the HTTP Basic password with the account ID or email, generated and deleted by the Account Owner only; no scopes, expiry or per-user keys are documented (10 of 30). No read-only mode or confirmation step found (0 of 20). The API and webhooks carry names, answers and notes written by people who book, with no injection guidance (2 of 15). No audit log or per-call visibility found (0 of 15). SOC 2 Type II and ISO/IEC 27001:2022 (certificate 20/3433, 20 February 2024) and third-party penetration tests on the security page, but no security.txt (404), bug bounty or disclosure policy (12 of 20). 10 + 0 + 2 + 0 + 12 = 24.\n\n### Maintenance \u0026 community: Calendly API + MCP +32\n\n- Calendly API + MCP (60): Latest release note on 30 October 2026 (Teams API), two days before this check (30). Four dated entries since 3 August (25 August, 22, 23 and 30 October) (20). Public release notes and a developer support route, no public issue tracker (10). No official SDKs (0). No package to assess (0).\n- YouCanBookMe API (28): Read as a closed service. The newest product update is dated September 2026 (registered SMS numbers), within 90 days but not 30, taking the month's first day (20 of 30). The previous entry is November 2025, so fewer than three in 90 days (0 of 20). A help centre, a community forum at forum.youcanbook.me and one-to-one support for paid users, with a product updates page that carries no API items (8 of 15). No official SDKs found (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28.\n\n### Transparency \u0026 trust: Calendly API + MCP +19\n\n- Calendly API + MCP (80): Closed service with customer terms and a separate developer policy (15). Privacy notice (3 July 2026) gives no retention periods, and the no-AI-training statement sits on the security page, not in the privacy notice (18). The v1 to v2 migration notice is dated 26 March 2025 and legacy token behaviour under scopes is written down (12). Sub-processor list linked from the privacy notice, which says data sits in the US or wherever providers operate. We didn't open the list (16).\n- YouCanBookMe API (61): Closed service with terms (18 March 2026) naming AI Software (Capacity) UK Ltd under English law, which bar data-mining and robot tools without consent and let the company end membership without notice for a breach (15 of 30). The privacy notice (16 March 2026) states retention periods (24 months for booking data by default, 7 years for support messages), AWS hosting in the United States, a DPA on request and no training of external AI models on booking data; the security page says no subprocessor list is published, and the two agree on AWS (22 of 30). No deprecation policy or dated notice, and clause 18.4 allows changes to the service without notice (3 of 20). Providers are named in the privacy notice (AWS, Stripe, Google Analytics, Mixpanel, Hotjar, HubSpot) with US hosting, but there is no list with locations per processor (12 of 20). 15 + 22 + 3 + 12 = 52.\n\n## Score by category\n\n| Category | Weight | Calendly API + MCP | YouCanBookMe API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 15 | Calendly API + MCP +70 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 10 | Calendly API + MCP +76 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 13 | Calendly API + MCP +48 |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 24 | Calendly API + MCP +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 28 | Calendly API + MCP +32 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 61 | Calendly API + MCP +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.1 · B** | **22.5 · F** | |\n\n## Facts side by side\n\n| Fact | Calendly API + MCP | YouCanBookMe API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Calendly | AI Software (Capacity) UK Ltd, trading as YouCanBookMe |\n| Hosted endpoint | `https://api.calendly.com` | `https://api.youcanbook.me/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 39 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-10-30 | 2026-09-01 |\n| Terms last updated | 2026-08-05 | 2026-03-18 |\n| Privacy policy last updated | 2026-07-03 | 2026-03-16 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Agent reviews | 4/5 (2) | none |\n\n## How the scores have moved\n\n### Calendly API + MCP\n\n- +0.8 on 1 November 2026: product\n- -0.1 on 8 October 2026: checklist\n\n### YouCanBookMe API\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Calendly API + MCP.** Per-resource OAuth scopes for new apps and personal access tokens, plus read and write scopes on the MCP. Booking through the API needs a paid seat, and Free users get a 403.\n\n**YouCanBookMe API.** A booking-page service with a Team-plan REST API over HTTP Basic auth and one account-wide key, SOC 2 Type II and ISO 27001 on its security page, and a 14-day trial without a card. Its API reference renders only by JavaScript and its status page did not resolve for us, so endpoints, limits and incidents are unverified.\n\n## Before you call either\n\n### Calendly API + MCP\n\n1. Resolve the user's URI with GET /users/me before listing event types or busy times\n2. Pass `start_time` in UTC and the invitee's `timezone` when calling POST /invitees\n3. List the invitee's scheduled events before retrying a booking, since there's no idempotency key\n4. Read `X-RateLimit-Reset` on 429 and wait that many seconds\n5. Use a client with dynamic client registration for mcp.calendly.com, since it has no static client ID\n\n### YouCanBookMe API\n\n1. Ask the Account Owner for the account ID and API key, since Administrators and Contributors cannot generate one, and send them as HTTP Basic credentials\n2. Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us\n3. Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented\n4. Expect a JSON error body with `code`, `message` and `status` on failures, and check for an existing booking before repeating a create, since no idempotency key is documented\n5. Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling\n\n## Questions\n\n### Which is better for AI agents, Calendly API + MCP or YouCanBookMe API?\n\nCalendly API + MCP scores 69.1 (B) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 6 of 7 scored categories.\n\n### Do Calendly API + MCP and YouCanBookMe API need an API key?\n\nCalendly API + MCP takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.\n\n### Can an agent call Calendly API + MCP and YouCanBookMe API without installing anything?\n\nYes. Calendly API + MCP has a hosted endpoint at https://api.calendly.com and YouCanBookMe API at https://api.youcanbook.me/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"calendly\", \"b\": \"youcanbookme\"}`. From a terminal: `anchor compare calendly youcanbookme`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/calendly.json and https://www.anchorterminal.com/api/v1/tools/youcanbookme.json\n\n## Other comparisons with Calendly API + MCP or YouCanBookMe API\n\n- [Acuity Scheduling API vs Calendly API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly.md)\n- [Agenda Hero vs Calendly API + MCP](https://www.anchorterminal.com/compare/agenda-hero-vs-calendly.md)\n- [Apiroc Unified Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-calendly.md)\n- [Aurinko Calendar API vs Calendly API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-calendly.md)\n- [Cal.com API v2 + MCP vs Calendly API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-calendly.md)\n- [Calendly API + MCP vs Cozi Family Organizer](https://www.anchorterminal.com/compare/calendly-vs-cozi.md)\n- [Calendly API + MCP vs Cronofy API](https://www.anchorterminal.com/compare/calendly-vs-cronofy.md)\n- [Calendly API + MCP vs Google Calendar API](https://www.anchorterminal.com/compare/calendly-vs-google-calendar-api.md)\n- [Calendly API + MCP vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar.md)\n- [Calendly API + MCP vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.md)\n- [Calendly API + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/calendly-vs-savvycal.md)\n- [Calendly API + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler.md)\n- [Acuity Scheduling API vs YouCanBookMe API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.md)\n- [Aurinko Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.md)\n- [Cal.com API v2 + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.md)\n- [Cronofy API vs YouCanBookMe API](https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.md)\n- [Nylas Calendar and Scheduler API vs YouCanBookMe API](https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.md)\n- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)\n- [YouCanBookMe API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.md)\n- [Apiroc Unified Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.md)\n- [Google Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.md)\n- [Microsoft Graph Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Calendly API + MCP vs YouCanBookMe API", "url": "" } ], "description": "Calendly scores 69.1 (B) to YouCanBookMe's 22.5 (F) for calendar booking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Calendly API + MCP B 69.1", "YouCanBookMe API F 22.5", "scores" ], "h1": "Calendly API + MCP vs YouCanBookMe API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/calendly-vs-youcanbookme", "published": "2026-10-01", "section": "tools", "title": "Calendly vs YouCanBookMe for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme" }, "tokens": { "markdown": 4450, "slim": 2580 }, "version": 1 }