{ "data": { "a": { "slug": "savvycal", "name": "SavvyCal API + MCP", "vendor": "SavvyCal, Inc.", "vendorUrl": "https://savvycal.com", "kind": "http-api", "category": "scheduling", "summary": "SavvyCal's scheduling API lists and books events on scheduling links, reads open time slots and manages links, webhooks and workflows, with a hosted MCP server that lets an assistant book, move and cancel meetings.", "url": "https://www.anchorterminal.com/tools/savvycal", "markdownUrl": "https://www.anchorterminal.com/tools/savvycal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/savvycal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/savvycal.json", "dns": "savvycal.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.savvycal.com/v1", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens (`pt_secret_...`) made in Settings \u003e Developers, or OAuth 2 authorisation code apps registered there, both sent as `Authorization: Bearer`. OAuth access tokens last 2 hours with a refresh token, and the spec declares no scopes for either. The MCP server at https://savvycal.com/mcp signs in with OAuth 2.1 (PKCE S256, dynamic client registration, scopes `mcp:read` and `mcp:write`, a revocation endpoint) and needs no key.", "pricing": "freemium", "pricingNotes": "The API, webhooks and the MCP server are on every plan including Free, per the plans page. Free accounts connect calendars, make links and run polls, but people can only book a link on Basic ($12 a user a month, $120 a year) or Premium ($20 a user a month, $200 a year). No self-serve trial, a 30-day money-back guarantee instead, and no card is mentioned for Free. 25 per cent off for students, educators and nonprofits.", "priceSummary": "$12 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI spec at api.savvycal.com/v1/spec or the pricing page (checked 2026-11-03). The spec has no 402 response.", "endpoints": [] }, "toolCount": 63, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.savvycal.com/developers", "llmsTxt": "https://docs.savvycal.com/llms.txt", "openapi": "https://api.savvycal.com/v1/spec", "capabilities": [ "calendar.booking", "calendar.availability", "calendar.read", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "oauth", "llms-txt", "openapi", "webhooks", "status-page", "security-txt", "closed-source" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 57, "grade": "C", "agentReady": false, "rank": 724, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 40, "payments": 30, "reliability": 70, "schema": 74, "security": 50, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.", "bestFor": "An agent booking on a person's SavvyCal links or driving their account through the MCP server.", "strengths": [ "OpenAPI 3.0.0 spec at api.savvycal.com/v1/spec, llms.txt and a Markdown twin of every docs page", "Hosted MCP server with OAuth 2.1, PKCE, dynamic client registration and `mcp:read` and `mcp:write` scopes, included on every plan", "Webhooks signed with HMAC-SHA256, retried up to 20 times with exponential backoff, over 16 event types", "Status page with calendar connection components and no notices from June to November 2026", "The MCP docs say the assistant asks for confirmation before cancelling meetings, deleting links or inviting teammates" ], "weaknesses": [ "No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)", "No idempotency keys, Retry-After header or official SDK", "No SOC 2 or ISO 27001 certification and no bug bounty, per the security page", "OAuth apps and personal access tokens carry no scopes, so a REST token reaches everything the user can", "Only one dated product update in the 90 days to 3 November 2026, and no API changelog" ], "agentNotes": [ "Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422", "Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After", "Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default", "Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads", "Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57 } ], "editorialScores": { "ergonomics": 53, "maintenance": 40, "payments": 30, "reliability": 70, "schema": 74, "security": 50, "transparency": 57 }, "provenanceScore": 89, "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 https://api.savvycal.com/v1/me -H \"Authorization: Bearer $SAVVYCAL_TOKEN\"", "claudeCode": "claude mcp add --transport http savvycal https://savvycal.com/mcp", "config": { "mcpServers": { "savvycal": { "url": "https://savvycal.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/calendar.booking", "tool": "https://letme.dev/savvycal" }, "area": "everyday", "unitPrices": [ { "item": "Basic", "unit": "seat-month", "usd": 12, "note": "$120 a user a year billed annually" }, { "item": "Premium", "unit": "seat-month", "usd": 20, "note": "$200 a user a year billed annually" } ], "provenance": { "legalEntity": "SavvyCal, Inc.", "domain": "savvycal.com", "domainRegistered": "2020-08-12", "endpointOnVendorDomain": true, "terms": "https://savvycal.com/terms", "privacy": "https://savvycal.com/privacy", "statusPage": "https://savvycal.instatus.com", "changelog": "https://feedback.savvycal.com/updates", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The terms (last updated 21 January 2026) name SavvyCal, Inc. under Minnesota law with AAA arbitration. They forbid access through automated or non-human means and the use of bots, scrapers or data-extraction tools, and do not mention the API, which the separate developer docs cover. Recorded as a fact; the public pages were read.", "savvycal.com/robots.txt disallows /events/ for every crawler, names ClaudeBot and anthropic-ai among twelve AI crawlers with the same rule, and sets Content-Signal ai-train=no, search=yes, ai-input=yes. docs.savvycal.com allows all with ai-train=yes. Nothing under /events/ was fetched.", "The privacy policy (17 October 2026) names SavvyCal, Inc., US servers, Stripe, OpenAI for advertising measurement, and a DPA with Standard Contractual Clauses. The DPA page is dated 16 January 2023.", "RDAP gives savvycal.com a registration date of 12 August 2020.", "security.txt at savvycal.com/.well-known/security.txt names security@savvycal.com, expires 2 May 2027 and points to savvycal.com/security.", "The status page is savvycal.instatus.com (Instatus), linked from the site footer. The What's New board at feedback.savvycal.com/updates is the product changelog." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/savvycal.json", "live": { "slug": "savvycal", "probe": { "target": "https://api.savvycal.com/v1", "method": "get", "lastAt": "2026-11-04T21:39:45.046752337Z", "lastOk": true, "lastStatus": 404, "lastMs": 130, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 166, "p95ms24h": 237, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://savvycal.instatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:26:44.192765993Z" }, "securityTxt": { "url": "https://savvycal.com/.well-known/security.txt", "state": "valid", "expires": "2027-05-03T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:05.808454415Z" }, "updatedAt": "2026-11-04T21:39:45.046752337Z" } }, "answer": "SavvyCal API + MCP scores 57 (C) on agent readiness against Zoom Scheduler API's 50.7 (D), and leads in 6 of 7 scored categories.", "b": { "slug": "zoom-scheduler", "name": "Zoom Scheduler API", "vendor": "Zoom Communications, Inc.", "vendorUrl": "https://www.zoom.com", "kind": "http-api", "category": "scheduling", "summary": "Zoom's REST API for Zoom Scheduler, its appointment booking product. It reads schedules, availability and scheduled events, lists open slots, creates and cancels bookings and sends booking webhooks, with OAuth access on api.zoom.us.", "url": "https://www.anchorterminal.com/tools/zoom-scheduler", "markdownUrl": "https://www.anchorterminal.com/tools/zoom-scheduler.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zoom-scheduler.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zoom-scheduler.json", "dns": "zoom-scheduler.grade.anchorterminal.com", "license": "Proprietary service under the Zoom API Licence and Terms of Use", "transports": [ "http" ], "remoteUrl": "https://api.zoom.us/v2", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 only. A person creates an app in the Zoom App Marketplace and picks Scheduler scopes. User apps use the authorisation code grant (PKCE supported) and get one-hour access tokens with 90-day refresh tokens. Server-to-Server OAuth apps exchange an account ID, client ID and client secret for a one-hour token with no user step, and an account administrator authorises the scopes. Granular scopes exist per operation, each with an `:admin` variant. The docs show refresh tokens and device codes sent as URL query parameters as one option.", "pricing": "paid", "pricingNotes": "Scheduler costs $5.99 a user a month, or $4.99 billed yearly, and is included in Workplace Business ($21.99 monthly). The pricing page lists \"Connect to Scheduler APIs\" under the paid Scheduler plan. Scheduler Basic is free with no card, with one booking page and one calendar, and whether it can call the API was not established. A 14-day trial is advertised. No per-call charge was found (checked 2026-10-09).", "priceSummary": "$5.99 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Scheduler reference, the rate limit and OAuth docs or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://developers.zoom.us/docs/api/scheduler/", "llmsTxt": "https://developers.zoom.us/llms.txt", "capabilities": [ "calendar.read", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "paid", "free-plan", "rest", "oauth", "webhooks", "llms-txt", "closed-source", "status-page", "soc2", "bug-bounty" ], "lastRelease": "2026-08-17", "graded": true, "anchor": { "graded": true, "score": 50.7, "grade": "D", "agentReady": false, "rank": 932, "ranked": true, "rankOf": 1349, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 43, "maintenance": 28, "payments": 25, "reliability": 63, "schema": 61, "security": 54, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "Each of the 24 operations has its own granular OAuth scope, and Zoom Scheduler and the REST API are separate components on the status page. No operation moves a booking, no official SDK covers Scheduler, and Zoom's API terms forbid benchmarking or monitoring the service.", "bestFor": "An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.", "strengths": [ "Granular OAuth scopes per operation, with separate read, write, update and delete scopes and user and admin variants", "A slot lookup (`GET /scheduler/schedules/{scheduleId}/available_times`) and a booking call (`POST /scheduler/attendee`), added in July and June 2026", "llms.txt and a Markdown copy of the full reference, with request examples and 400, 401, 404, 409, 429 and 500 responses listed", "Rate limits published by plan. Every Scheduler operation is labelled Light, 30 requests a second on Pro", "SOC 2 Type 2 report (October 2024 to October 2025) names Zoom Scheduler and Zoom APIs in scope, and security.txt is valid to 2029" ], "weaknesses": [ "Zoom's API terms (section 3.7.9) forbid using the APIs to monitor availability or performance, or for benchmarking. This matters before any probe is run", "No operation moves a booking. `PATCH /scheduler/events/{eventId}` changes status, notes and no-show marks only", "No idempotency key or safe-retry guidance for booking writes was found in the reviewed documentation", "No official SDK covers Scheduler. Zoom Rivet 0.3.0 has no Scheduler module", "No downloadable OpenAPI file is linked, and the Markdown reference omits query and path parameters", "The API terms allow Zoom to change or deprecate APIs without prior notice and disclaim any uptime guarantee" ], "agentNotes": [ "Call `GET /scheduler/schedules/{scheduleId}/available_times` and book only a spot whose status is `available`", "Send `start_date_time` in ISO 8601 with the booker's IANA `time_zone` to `POST /scheduler/attendee`. Expect 409 on a conflict", "To move a booking, cancel it with `PATCH /scheduler/events/{eventId}` and `status` set to `cancelled`, then book the new slot", "List scheduled events before retrying a booking, because no idempotency key is documented", "Request a new Server-to-Server OAuth token every hour. That grant issues no refresh token" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.7 } ], "editorialScores": { "ergonomics": 43, "maintenance": 28, "payments": 25, "reliability": 63, "schema": 61, "security": 54, "transparency": 59 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-28", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"Authorization: Bearer $ZOOM_ACCESS_TOKEN\" \"https://api.zoom.us/v2/scheduler/schedules\"" }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/zoom-scheduler" }, "area": "everyday", "unitPrices": [ { "item": "Zoom Scheduler (the plan that lists Scheduler API access)", "unit": "seat-month", "usd": 5.99, "note": "Monthly billing. $4.99 a user a month billed yearly" } ], "provenance": { "legalEntity": "Zoom Communications, Inc.", "domain": "zoom.us", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.zoom.com/en/trust/legal/zoom-api-license-and-tou/", "privacy": "https://www.zoom.com/en/trust/privacy/privacy-statement/", "statusPage": "https://status.zoom.us", "changelog": "https://developers.zoom.us/changelog/", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Zoom API Licence and Terms of Use (last updated 16 July 2025) and the Privacy Statement (last updated 17 September 2026) both name Zoom Communications, Inc., 55 Almaden Blvd, Suite 600, San Jose, CA 95113.", "The API answers at https://api.zoom.us/v2 and tokens are issued at https://zoom.us/oauth/token. Legal pages sit on www.zoom.com.", "zoom.us/.well-known/security.txt gives a report form, security-reports@zoom.us, a PGP key and an expiry of 31 December 2029.", "status.zoom.us redirects to www.zoomstatus.com, an Atlassian Statuspage site.", "The registration date of zoom.us was not established. rdap.org answered 404 for the domain.", "The account holder's use of Scheduler itself falls under the Zoom Terms of Service (effective 11 August 2023), which the API terms cite for the definition of Customer Content." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zoom-scheduler.json", "live": { "slug": "zoom-scheduler", "probe": { "target": "https://api.zoom.us/v2", "method": "get", "lastAt": "2026-11-04T21:39:56.184795982Z", "lastOk": true, "lastStatus": 404, "lastMs": 154, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 175, "p95ms24h": 412, "samples24h": 247, "samples30d": 6569, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "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://status.zoom.us", "indicator": "maintenance", "summary": "Service Under Maintenance", "checkedAt": "2026-11-04T21:39:04.060842144Z" }, "securityTxt": { "url": "https://zoom.us/.well-known/security.txt", "state": "valid", "expires": "2029-12-31T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:47.603717684Z" }, "llmsTxt": { "url": "https://developers.zoom.us/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:24:39.9329938Z" }, "domain": { "domain": "zoom.us", "checkedAt": "2026-11-01T14:10:46.976026774Z" }, "pages": [ { "url": "https://developers.zoom.us/changelog/", "kind": "changelog", "status": 404, "checkedAt": "2026-11-04T08:19:39.320409659Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://www.zoom.com/en/trust/privacy/privacy-statement/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:47:58.882472991Z", "changedAt": "2026-10-22T01:39:12.393937492Z", "fingerprint": "c0d31e14e3ee" }, { "url": "https://www.zoom.com/en/trust/legal/zoom-api-license-and-tou/", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:47:56.427106898Z", "changedAt": "2026-10-22T01:39:09.991974204Z", "fingerprint": "62f6354085e2" } ], "updatedAt": "2026-11-04T21:39:56.184795982Z" } }, "edges": [ { "by": 13, "category": "schema", "leads": "savvycal", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.0.0 at api.savvycal.com/v1/spec covers all 22 operations with 56 schemas; the MCP tools' schemas could not be read without signing in (23 of 25). llms.txt and a Markdown twin of every docs page (10). Only 8 of the 22 operations carry a description, and those state constraints (events must match an open slot, an invalid filter resets every filter) rather than when to choose another endpoint (10 of 20). Required flags on 14 of 43 parameters, 34 enum properties across the schemas, `limit` bounded 1 to 100, `until` at most 31 days after `from` (12 of 15). Example values on parameters and a documented error shape keyed by field, with 400, 401, 404, 422 and 429 declared per operation, but no full response examples (10 of 15). A /v1 path and a promise that changes are additive, with dated product updates on the feedback board but no API changelog (9 of 15). 23 + 10 + 10 + 12 + 10 + 9 = 74.", "b": "The reference states OpenAPI version 3.1.1, but no specification file is linked from the page, the API catalogue or llms.txt. A Markdown copy of the whole reference is published (10). llms.txt, Markdown copies of pages and an API catalogue at `/.well-known/api-catalog.json` (10). Most operations carry one line such as \"Patches a scheduled event\". The available times and booking operations say when to use them (8). Request bodies are typed, with 55 required marks, 38 enumerated fields and email, date and date-time formats. The Markdown copy and the static page omit query and path parameters (9). Every request body has an example and each operation lists its error statuses with a code name, some misspelt (11). The path is versioned v2 and the changelog has dated Scheduler entries (13). Total 61." }, "scores": { "a": 74, "b": 61 } }, { "by": 12, "category": "maintenance", "leads": "savvycal", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40.", "b": "The latest Scheduler changelog entry is 17 August 2026, 53 days before this check (20). Two dated entries in the last 90 days, 13 July and 17 August (0). A public changelog with a developer forum thread for each entry and a developer support page. Whether the forum answers was not checked (8). No official SDK covers Scheduler (0). No package to assess (0). Total 28." }, "scores": { "a": 40, "b": 28 } }, { "by": 10, "category": "ergonomics", "leads": "savvycal", "name": "Agent ergonomics", "reasons": { "a": "List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53.", "b": "No field selection was found, and a schedule object runs to several hundred lines of fields. Query parameters could not be read (8). List responses return `next_page_token`, and the changelog records filters by team, account scope and created or updated time. The parameter list itself was not readable (14). Errors carry a status and a short code name such as InvalidArgument, NotFound or Conflict, with a 409 on booking conflicts and little detail (12). No idempotency key or safe-retry guidance for `POST /scheduler/attendee` (3). Booking needs six fields. No official SDK covers Scheduler, and Zoom Rivet 0.3.0 has no Scheduler module (6). Total 43." }, "scores": { "a": 53, "b": 43 } }, { "by": 7, "category": "reliability", "leads": "savvycal", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70.", "b": "Graded as a hosted API. Statuspage site at status.zoom.us (redirects to www.zoomstatus.com) with Zoom Scheduler as its own component and REST API and Webhooks under Zoom Developer Platform (20). The front page shows 25 September to 9 October 2026, with no incident naming Scheduler or the REST API. The developer documentation site was degraded for 1 hour 54 minutes on 3 October. The history page is drawn by script and the status API is closed by robots.txt, so 90 days could not be read (10). Every Scheduler operation is labelled Light, which is 4 a second and 6,000 a day on Free, 30 a second on Pro and 80 a second on Business and above, per account (15). The docs say to wait and retry on 429 and that the daily-limit response carries a header saying when to resume. No `Retry-After` is named and no idempotency key exists for booking writes (8). No SLA found, and the API terms say Zoom does not guarantee uptime (0). No beta label on the Scheduler API, and Zoom's lifecycle page treats an initial release as stable (10). Total 63." }, "scores": { "a": 70, "b": 63 } }, { "by": 5, "category": "payments", "leads": "savvycal", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-seat plan prices public, nothing per call (10). A Free plan with the API, webhooks and MCP server included and no card mentioned, though booking through a link needs Basic or Premium and there is no self-serve trial (20). A person signs up in a browser and approves the OAuth consent (0). 0 + 10 + 20 + 0 = 30.", "b": "No x402, MPP or L402 (0). Seat prices are public, $5.99 a user a month or $4.99 billed yearly, with nothing per call (10). Scheduler Basic is free with no card and a 14-day trial is advertised, but the pricing page lists API access under the paid plan and whether the free plan or the trial can call the API was not established (15). A person signs up and creates a Marketplace app in a browser (0). Total 25." }, "scores": { "a": 30, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "SavvyCal, Inc.", "b": "Zoom Communications, Inc.", "name": "Vendor" }, { "a": "https://api.savvycal.com/v1", "b": "https://api.zoom.us/v2", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the Zoom API Licence and Terms of Use", "name": "Licence" }, { "a": "63", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-27", "b": "2026-08-17", "name": "Last release" }, { "a": "2026-01-21", "b": "2025-07-16", "name": "Terms last updated" }, { "a": "2026-10-17", "b": "2026-09-17", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "SavvyCal API + MCP scores 57 (C) on agent readiness against Zoom Scheduler API's 50.7 (D), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, SavvyCal API + MCP or Zoom Scheduler API?" }, { "answer": "SavvyCal API + MCP takes an API key or an OAuth sign-in. Zoom Scheduler API uses an OAuth sign-in.", "question": "Do SavvyCal API + MCP and Zoom Scheduler API need an API key?" }, { "answer": "Yes. SavvyCal API + MCP has a hosted endpoint at https://api.savvycal.com/v1 and Zoom Scheduler API at https://api.zoom.us/v2.", "question": "Can an agent call SavvyCal API + MCP and Zoom Scheduler API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 63", "Schema \u0026 documentation, 74 against 61", "Agent ergonomics, 53 against 43", "Payments \u0026 pricing, 30 against 25", "Maintenance \u0026 community, 40 against 28" ], "also": [ "Free to start without a card" ], "goodFor": "An agent booking on a person's SavvyCal links or driving their account through the MCP server.", "slug": "savvycal", "watchFor": "No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)" }, { "aheadOn": null, "also": null, "goodFor": "An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.", "slug": "zoom-scheduler", "watchFor": "Zoom's API terms (section 3.7.9) forbid using the APIs to monitor availability or performance, or for benchmarking. This matters before any probe is run" } ], "history": { "savvycal": null, "zoom-scheduler": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": 0, "from": 50.7, "fromGrade": "D", "to": 50.7, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50.6, "fromGrade": "D", "to": 50.7, "toGrade": "D" } ] }, "job": { "capability": "calendar.booking", "name": "Calendar booking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.json", "title": "Acuity Scheduling API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler.json", "title": "Acuity Scheduling API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.json", "title": "Agenda Hero vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-zoom-scheduler.json", "title": "Agenda Hero vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-savvycal.json", "title": "Apiroc Unified Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/apiroc-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-zoom-scheduler.json", "title": "Apiroc Unified Calendar API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.json", "title": "Aurinko Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-zoom-scheduler.json", "title": "Aurinko Calendar API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-savvycal.json", "title": "Cal.com API v2 + MCP vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cal-com-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler.json", "title": "Cal.com API v2 + MCP vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler" }, { "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/cozi-vs-savvycal.json", "title": "Cozi Family Organizer vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cozi-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-zoom-scheduler.json", "title": "Cozi Family Organizer vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/cozi-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-savvycal.json", "title": "Cronofy API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cronofy-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-zoom-scheduler.json", "title": "Cronofy API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.json", "title": "Google Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-zoom-scheduler.json", "title": "Google Calendar API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.json", "title": "Microsoft Graph Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.json", "title": "Microsoft Graph Calendar API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.json", "title": "Nylas Calendar and Scheduler API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.json", "title": "Nylas Calendar and Scheduler API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler" }, { "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" } ], "panel": null, "scores": [ { "by": 7, "edge": "savvycal", "key": "reliability", "name": "Reliability", "savvycal": 70, "weight": 16, "zoom-scheduler": 63 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "savvycal", "key": "schema", "name": "Schema \u0026 documentation", "savvycal": 74, "weight": 13, "zoom-scheduler": 61 }, { "by": 10, "edge": "savvycal", "key": "ergonomics", "name": "Agent ergonomics", "savvycal": 53, "weight": 13, "zoom-scheduler": 43 }, { "by": 4, "edge": "zoom-scheduler", "key": "security", "name": "Security \u0026 auth", "savvycal": 50, "weight": 14, "zoom-scheduler": 54 }, { "by": 5, "edge": "savvycal", "key": "payments", "name": "Payments \u0026 pricing", "savvycal": 30, "weight": 10, "zoom-scheduler": 25 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "savvycal", "key": "maintenance", "name": "Maintenance \u0026 community", "savvycal": 40, "weight": 7, "zoom-scheduler": 28 }, { "by": 3, "edge": "savvycal", "key": "transparency", "name": "Transparency \u0026 trust", "savvycal": 73, "weight": 7, "zoom-scheduler": 70 } ], "summary": "SavvyCal API + MCP scores 57 (C) on agent readiness against Zoom Scheduler API's 50.7 (D), and leads in 6 of 7 scored categories. Both do calendar booking.", "tasks": null, "tutorials": [], "verdicts": { "savvycal": "A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.", "zoom-scheduler": "Each of the 24 operations has its own granular OAuth scope, and Zoom Scheduler and the REST API are separate components on the status page. No operation moves a booking, no official SDK covers Scheduler, and Zoom's API terms forbid benchmarking or monitoring the service." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler", "json": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.min.md" }, "markdown": "SavvyCal API + MCP scores 57 (C) on agent readiness against Zoom Scheduler API's 50.7 (D), and leads in 6 of 7 scored categories. Both do calendar booking.\n\n- SavvyCal API + MCP: grade C, 57/100, rank #724 of 1349. Markdown https://www.anchorterminal.com/tools/savvycal.md · JSON https://www.anchorterminal.com/api/v1/tools/savvycal.json\n- Zoom Scheduler API: grade D, 50.7/100, rank #932 of 1349. Markdown https://www.anchorterminal.com/tools/zoom-scheduler.md · JSON https://www.anchorterminal.com/api/v1/tools/zoom-scheduler.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### SavvyCal API + MCP (C)\n\nGood for: An agent booking on a person's SavvyCal links or driving their account through the MCP server.\n\nAhead on:\n- Reliability, 70 against 63\n- Schema \u0026 documentation, 74 against 61\n- Agent ergonomics, 53 against 43\n- Payments \u0026 pricing, 30 against 25\n- Maintenance \u0026 community, 40 against 28\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)\n\n### Zoom Scheduler API (D)\n\nGood for: An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.\n\nWatch for: Zoom's API terms (section 3.7.9) forbid using the APIs to monitor availability or performance, or for benchmarking. This matters before any probe is run\n\n\n## Why the edge\n\n### Schema \u0026 documentation: SavvyCal API + MCP +13\n\n- SavvyCal API + MCP (74): OpenAPI 3.0.0 at api.savvycal.com/v1/spec covers all 22 operations with 56 schemas; the MCP tools' schemas could not be read without signing in (23 of 25). llms.txt and a Markdown twin of every docs page (10). Only 8 of the 22 operations carry a description, and those state constraints (events must match an open slot, an invalid filter resets every filter) rather than when to choose another endpoint (10 of 20). Required flags on 14 of 43 parameters, 34 enum properties across the schemas, `limit` bounded 1 to 100, `until` at most 31 days after `from` (12 of 15). Example values on parameters and a documented error shape keyed by field, with 400, 401, 404, 422 and 429 declared per operation, but no full response examples (10 of 15). A /v1 path and a promise that changes are additive, with dated product updates on the feedback board but no API changelog (9 of 15). 23 + 10 + 10 + 12 + 10 + 9 = 74.\n- Zoom Scheduler API (61): The reference states OpenAPI version 3.1.1, but no specification file is linked from the page, the API catalogue or llms.txt. A Markdown copy of the whole reference is published (10). llms.txt, Markdown copies of pages and an API catalogue at `/.well-known/api-catalog.json` (10). Most operations carry one line such as \"Patches a scheduled event\". The available times and booking operations say when to use them (8). Request bodies are typed, with 55 required marks, 38 enumerated fields and email, date and date-time formats. The Markdown copy and the static page omit query and path parameters (9). Every request body has an example and each operation lists its error statuses with a code name, some misspelt (11). The path is versioned v2 and the changelog has dated Scheduler entries (13). Total 61.\n\n### Maintenance \u0026 community: SavvyCal API + MCP +12\n\n- SavvyCal API + MCP (40): Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40.\n- Zoom Scheduler API (28): The latest Scheduler changelog entry is 17 August 2026, 53 days before this check (20). Two dated entries in the last 90 days, 13 July and 17 August (0). A public changelog with a developer forum thread for each entry and a developer support page. Whether the forum answers was not checked (8). No official SDK covers Scheduler (0). No package to assess (0). Total 28.\n\n### Agent ergonomics: SavvyCal API + MCP +10\n\n- SavvyCal API + MCP (53): List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53.\n- Zoom Scheduler API (43): No field selection was found, and a schedule object runs to several hundred lines of fields. Query parameters could not be read (8). List responses return `next_page_token`, and the changelog records filters by team, account scope and created or updated time. The parameter list itself was not readable (14). Errors carry a status and a short code name such as InvalidArgument, NotFound or Conflict, with a 409 on booking conflicts and little detail (12). No idempotency key or safe-retry guidance for `POST /scheduler/attendee` (3). Booking needs six fields. No official SDK covers Scheduler, and Zoom Rivet 0.3.0 has no Scheduler module (6). Total 43.\n\n### Reliability: SavvyCal API + MCP +7\n\n- SavvyCal API + MCP (70): Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70.\n- Zoom Scheduler API (63): Graded as a hosted API. Statuspage site at status.zoom.us (redirects to www.zoomstatus.com) with Zoom Scheduler as its own component and REST API and Webhooks under Zoom Developer Platform (20). The front page shows 25 September to 9 October 2026, with no incident naming Scheduler or the REST API. The developer documentation site was degraded for 1 hour 54 minutes on 3 October. The history page is drawn by script and the status API is closed by robots.txt, so 90 days could not be read (10). Every Scheduler operation is labelled Light, which is 4 a second and 6,000 a day on Free, 30 a second on Pro and 80 a second on Business and above, per account (15). The docs say to wait and retry on 429 and that the daily-limit response carries a header saying when to resume. No `Retry-After` is named and no idempotency key exists for booking writes (8). No SLA found, and the API terms say Zoom does not guarantee uptime (0). No beta label on the Scheduler API, and Zoom's lifecycle page treats an initial release as stable (10). Total 63.\n\n### Payments \u0026 pricing: SavvyCal API + MCP +5\n\n- SavvyCal API + MCP (30): No x402, MPP or L402 (0). Per-seat plan prices public, nothing per call (10). A Free plan with the API, webhooks and MCP server included and no card mentioned, though booking through a link needs Basic or Premium and there is no self-serve trial (20). A person signs up in a browser and approves the OAuth consent (0). 0 + 10 + 20 + 0 = 30.\n- Zoom Scheduler API (25): No x402, MPP or L402 (0). Seat prices are public, $5.99 a user a month or $4.99 billed yearly, with nothing per call (10). Scheduler Basic is free with no card and a 14-day trial is advertised, but the pricing page lists API access under the paid plan and whether the free plan or the trial can call the API was not established (15). A person signs up and creates a Marketplace app in a browser (0). Total 25.\n\n## Score by category\n\n| Category | Weight | SavvyCal API + MCP | Zoom Scheduler API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 63 | SavvyCal API + MCP +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 61 | SavvyCal API + MCP +13 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 43 | SavvyCal API + MCP +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 54 | Zoom Scheduler API +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | SavvyCal API + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 28 | SavvyCal API + MCP +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 70 | SavvyCal API + MCP +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57 · C** | **50.7 · D** | |\n\n## Facts side by side\n\n| Fact | SavvyCal API + MCP | Zoom Scheduler API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | SavvyCal, Inc. | Zoom Communications, Inc. |\n| Hosted endpoint | `https://api.savvycal.com/v1` | `https://api.zoom.us/v2` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | none | Proprietary service under the Zoom API Licence and Terms of Use |\n| Tools exposed | 63 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-27 | 2026-08-17 |\n| Terms last updated | 2026-01-21 | 2025-07-16 |\n| Privacy policy last updated | 2026-10-17 | 2026-09-17 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n\n## How the scores have moved\n\n### SavvyCal API + MCP\n\nNo score change since it was listed.\n\n### Zoom Scheduler API\n\n- no change on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**SavvyCal API + MCP.** A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.\n\n**Zoom Scheduler API.** Each of the 24 operations has its own granular OAuth scope, and Zoom Scheduler and the REST API are separate components on the status page. No operation moves a booking, no official SDK covers Scheduler, and Zoom's API terms forbid benchmarking or monitoring the service.\n\n## Before you call either\n\n### SavvyCal API + MCP\n\n1. Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422\n2. Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After\n3. Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default\n4. Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads\n5. Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly\n\n### Zoom Scheduler API\n\n1. Call `GET /scheduler/schedules/{scheduleId}/available_times` and book only a spot whose status is `available`\n2. Send `start_date_time` in ISO 8601 with the booker's IANA `time_zone` to `POST /scheduler/attendee`. Expect 409 on a conflict\n3. To move a booking, cancel it with `PATCH /scheduler/events/{eventId}` and `status` set to `cancelled`, then book the new slot\n4. List scheduled events before retrying a booking, because no idempotency key is documented\n5. Request a new Server-to-Server OAuth token every hour. That grant issues no refresh token\n\n## Questions\n\n### Which is better for AI agents, SavvyCal API + MCP or Zoom Scheduler API?\n\nSavvyCal API + MCP scores 57 (C) on agent readiness against Zoom Scheduler API's 50.7 (D), and leads in 6 of 7 scored categories.\n\n### Do SavvyCal API + MCP and Zoom Scheduler API need an API key?\n\nSavvyCal API + MCP takes an API key or an OAuth sign-in. Zoom Scheduler API uses an OAuth sign-in.\n\n### Can an agent call SavvyCal API + MCP and Zoom Scheduler API without installing anything?\n\nYes. SavvyCal API + MCP has a hosted endpoint at https://api.savvycal.com/v1 and Zoom Scheduler API at https://api.zoom.us/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.json, and with the fewest tokens: https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"savvycal\", \"b\": \"zoom-scheduler\"}`. From a terminal: `anchor compare savvycal zoom-scheduler`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/savvycal.json and https://www.anchorterminal.com/api/v1/tools/zoom-scheduler.json\n\n## Other comparisons with SavvyCal API + MCP or Zoom Scheduler API\n\n- [Acuity Scheduling API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.md)\n- [Acuity Scheduling API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler.md)\n- [Agenda Hero vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.md)\n- [Agenda Hero vs Zoom Scheduler API](https://www.anchorterminal.com/compare/agenda-hero-vs-zoom-scheduler.md)\n- [Apiroc Unified Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-savvycal.md)\n- [Apiroc Unified Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-zoom-scheduler.md)\n- [Aurinko Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.md)\n- [Aurinko Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-zoom-scheduler.md)\n- [Cal.com API v2 + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-savvycal.md)\n- [Cal.com API v2 + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler.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- [Cozi Family Organizer vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cozi-vs-savvycal.md)\n- [Cozi Family Organizer vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cozi-vs-zoom-scheduler.md)\n- [Cronofy API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cronofy-vs-savvycal.md)\n- [Cronofy API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-zoom-scheduler.md)\n- [Google Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.md)\n- [Google Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/google-calendar-api-vs-zoom-scheduler.md)\n- [Microsoft Graph Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.md)\n- [Microsoft Graph Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.md)\n- [Nylas Calendar and Scheduler API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.md)\n- [Nylas Calendar and Scheduler API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.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", "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": "SavvyCal API + MCP vs Zoom Scheduler API", "url": "" } ], "description": "SavvyCal scores 57 (C) to Zoom Scheduler's 50.7 (D) for calendar booking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "SavvyCal API + MCP C 57", "Zoom Scheduler API D 50.7", "scores" ], "h1": "SavvyCal API + MCP vs Zoom Scheduler API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/savvycal-vs-zoom-scheduler", "published": "2026-10-01", "section": "tools", "title": "SavvyCal vs Zoom Scheduler for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler" }, "tokens": { "markdown": 4350, "slim": 2330 }, "version": 1 }