# Google Calendar API vs YouCanBookMe API

> Google Calendar scores 79.7 (A) to YouCanBookMe's 22.5 (F) for calendar availability. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme
- Markdown: https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.md (~5,000 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

Google Calendar API scores 79.7 (A) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category. Both do calendar availability.

- Google Calendar API: grade A, 79.7/100, rank #10 of 1349. Markdown https://www.anchorterminal.com/tools/google-calendar-api.md · JSON https://www.anchorterminal.com/api/v1/tools/google-calendar-api.json
- YouCanBookMe API: grade F, 22.5/100, rank #1286 of 1349. Markdown https://www.anchorterminal.com/tools/youcanbookme.md · JSON https://www.anchorterminal.com/api/v1/tools/youcanbookme.json
- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md
- All 89 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md

## Which one, for what

### Google Calendar API (A)

Good for: An agent acting on Google Workspace or Gmail users' own calendars with tight scopes and no per-account fee.

Ahead on:
- Reliability, 90 against 15
- Schema & documentation, 88 against 10
- Agent ergonomics, 91 against 13
- Security & auth, 77 against 24
- Payments & pricing, 35 against 30
- Maintenance & community, 87 against 28
- Transparency & trust, 82 against 61

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Google calendars only

### YouCanBookMe API (F)

Good for: A booking-page product for small businesses, closest to calendly and savvycal in scheduling.

Also in its favour:
- Free to start without a card

Watch 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


## Why the edge

### Schema & documentation: Google Calendar API +78

- Google Calendar API (88): Google publishes a discovery document rather than OpenAPI, which is a machine-readable contract all the same, at revision 20261028 on 1 November (25). No llms.txt, and developers.google.com/llms.txt and /workspace/calendar/llms.txt returned 404 again on 1 November, but doc pages return Markdown when `.md.txt` is appended to the URL, which we found no index or link advertising, read as for Drive, Sheets and Forms (5 of 10). Reference pages say what each method does and when to use patch over update, but we couldn't read the MCP tool descriptions (15). Typed parameters with enums such as `orderBy` and `eventTypes` (13). An error page that gives each reason code a recommended action, from `timeRangeEmpty` to `fullSyncRequired` (15). v3 in the path and dated release notes, latest 12 October 2026, with nothing newer on 1 November (15).
- 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.

### Agent ergonomics: Google Calendar API +78

- Google Calendar API (91): Responses size with `maxResults` and Google's standard `fields` partial responses (20). `pageToken`, `syncToken`, `timeMin` and `timeMax`, `q` and `singleEvents` for expanding recurrences (20). Error reasons an agent can act on, with the action written next to each one (20). Client-supplied event IDs make creates safe to retry and ETags guard updates. We found no readOnlyHint or destructiveHint on the MCP's write tools (16). Official client libraries in many languages, and most parameters are optional (15).
- 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.

### Reliability: Google Calendar API +75

- Google Calendar API (90): The Google Workspace Status Dashboard lists Calendar with component history and an incidents feed (20). On 1 November the dashboard's 365-day list shows two Calendar incidents, 31 May 2026 (56 minutes, several Workspace products) and 13 March 2026 (2 hours 30 minutes of intermittent errors), with none in the 90 days to 1 November. Other Workspace products have incidents in August and September (Drive, Gmail, Chat, Classroom and Gemini), none naming Calendar. The dashboard tracks the Calendar product rather than the API alone (30). 10,000 requests a minute per project, 600 a minute per user per project and 1,000,000 a day per project, unchanged on 1 November (15). 403 and 429 `usageLimits` errors with a truncated exponential backoff formula, client-supplied event IDs that return 409 on a duplicate, and ETags with 412 on a stale write (15). No SLA for the API found (0). The REST API is GA. The MCP server is still a developer preview on 1 November (10).
- 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.

### Maintenance & community: Google Calendar API +59

- Google Calendar API (87): @googleapis/calendar 20.1.0 on 3 October 2026 is still the newest on npm on 1 November, 29 days earlier, and the discovery document has moved to revision 20261028 (30). Release notes on 12 October, plus client releases on 10, 14 and 24 September and 3 October, all within the 90 days to 1 November (the July notes have aged out) (20). Dated release notes and public client repositories with active maintainers (12). Current official client libraries (15). Generated clients rebuilt by CI in google-api-nodejs-client, with commits up to 30 October in a clone on 1 November (10).
- 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.

### Security & auth: Google Calendar API +53

- Google Calendar API (77): OAuth 2.0 with 20 Calendar scopes on the auth page, from `calendar.freebusy` and `calendar.events.owned.readonly` up to full `calendar`, and the discovery document (revision 20261028) carries a 21st, `calendar.settings`, which the auth page still doesn't list on 1 November (30), less 10 because the discovery document lists `oauth_token` and `key` as query parameters, the API also reads `access_token` from the query string, and Google's OAuth web-server guide shows the query string as an alternative to the header, read as for Gmail, Sheets and Forms (20). The auth page's table gives each scope's meaning only, and the non-sensitive, sensitive and restricted classes are per the 1 October check, not re-read on 4 or 17 October. Read-only and free/busy-only scopes, and the MCP guide (updated 29 October) still configures three read-only scopes. Nothing in the API confirms a delete (17). The MCP guide, updated 29 October, warns about indirect prompt injection and says prompts and responses must be screened, with Model Armor or a documented alternative, and tells operators to review AI-initiated actions (12). The Cloud console API dashboard shows traffic, errors by method and response code, and latency percentiles per project, but not a per-call log (8). Valid security.txt to 2030 with contacts and the Google VRP bug bounty policy, read on 1 November. Google's SOC 2 page sends customers to Compliance Reports Manager for the Google Workspace reports, and that Calendar is in their scope is per the 4 October check (20).
- 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.

### Transparency & trust: Google Calendar API +21

- Google Calendar API (82): Closed service under Google's API terms, with Apache-2.0 client libraries (15). Google's privacy policy covers end users, and the Workspace data processing terms cover tenants, but we didn't find one retention statement for Calendar API data (18). Dated announcements ahead of changes, such as the 1 June notice for the 29 June GA of `writerWithoutPrivateAccess` at least 90 days' notice promised before quota charges, and the 12 October notice that Workspace MCP servers reject OAuth clients not marked agentic from 11 November 2026 (15). The Workspace sub-processor list, last modified 19 October 2026, names Google group and third-party sub-processors with the countries each processes in, and covers Calendar as a Core Service for Workspace tenants (20).
- 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.

## Score by category

| Category | Weight | Google Calendar API | YouCanBookMe API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 15 | Google Calendar API +75 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 88 | 10 | Google Calendar API +78 |
| Agent ergonomics | 13% (16.2 this run) | 91 | 13 | Google Calendar API +78 |
| Security & auth | 14% (17.5 this run) | 77 | 24 | Google Calendar API +53 |
| Payments & pricing | 10% (12.5 this run) | 35 | 30 | Google Calendar API +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 87 | 28 | Google Calendar API +59 |
| Transparency & trust | 7% (8.8 this run) | 82 | 61 | Google Calendar API +21 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **79.7 · A** | **22.5 · F** | |

## Facts side by side

| Fact | Google Calendar API | YouCanBookMe API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Google | AI Software (Capacity) UK Ltd, trading as YouCanBookMe |
| Hosted endpoint | `https://www.googleapis.com/calendar/v3` | `https://api.youcanbook.me/v1` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (client libraries) | none |
| Tools exposed | 9 | none |
| Read-only variant documented | yes | yes |
| llms.txt | no | no |
| Last release | 2026-10-03 | 2026-09-01 |
| Terms last updated | 2021-11-09 | 2026-03-18 |
| Privacy policy last updated | 2026-10-01 | 2026-03-16 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 12k stars, 1M npm/wk | none |
| Agent reviews | 4/5 (8) | none |

## How the scores have moved

### Google Calendar API

- +0.1 on 28 October 2026: checklist
- -1.0 on 17 October 2026: correction
- -0.2 on 8 October 2026: checklist

### YouCanBookMe API

No score change since it was listed.

## Verdicts

**Google Calendar API.** 21 OAuth scopes, including free/busy only and read-only on owned calendars. Google calendars only.

**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.

## Before you call either

### Google Calendar API

1. Ask for `calendar.events.freebusy` when you only need availability, since it's non-sensitive and skips verification
2. Set your own event `id` on insert, and treat a 409 as already created
3. Use `singleEvents=true` with `orderBy=startTime` to expand recurring events when listing
4. On 410 `fullSyncRequired`, drop the stored `syncToken` and do a full sync
5. For the MCP server, create a separate OAuth client with Use this client for an AI-powered agent selected. From 11 November 2026 other clients are rejected

### YouCanBookMe API

1. 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
2. Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us
3. Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented
4. 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
5. Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling

## Questions

### Which is better for AI agents, Google Calendar API or YouCanBookMe API?

Google Calendar API scores 79.7 (A) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category.

### Do Google Calendar API and YouCanBookMe API need an API key?

Google Calendar API uses an OAuth sign-in. YouCanBookMe API needs an API key.

### Can an agent call Google Calendar API and YouCanBookMe API without installing anything?

Yes. Google Calendar API has a hosted endpoint at https://www.googleapis.com/calendar/v3 and YouCanBookMe API at https://api.youcanbook.me/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "google-calendar-api", "b": "youcanbookme"}`. From a terminal: `anchor compare google-calendar-api youcanbookme`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/google-calendar-api.json and https://www.anchorterminal.com/api/v1/tools/youcanbookme.json

## Other comparisons with Google Calendar API or YouCanBookMe API

- [Acuity Scheduling API vs Google Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-google-calendar-api.md)
- [Agenda Hero vs Google Calendar API](https://www.anchorterminal.com/compare/agenda-hero-vs-google-calendar-api.md)
- [Apiroc Unified Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-google-calendar-api.md)
- [Aurinko Calendar API vs Google Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-google-calendar-api.md)
- [Cal.com API v2 + MCP vs Google Calendar API](https://www.anchorterminal.com/compare/cal-com-vs-google-calendar-api.md)
- [Calendly API + MCP vs Google Calendar API](https://www.anchorterminal.com/compare/calendly-vs-google-calendar-api.md)
- [Cozi Family Organizer vs Google Calendar API](https://www.anchorterminal.com/compare/cozi-vs-google-calendar-api.md)
- [Cronofy API vs Google Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-google-calendar-api.md)
- [Google Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/google-calendar-api-vs-microsoft-graph-calendar.md)
- [Google Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/google-calendar-api-vs-nylas-calendar.md)
- [Google Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.md)
- [Google Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/google-calendar-api-vs-zoom-scheduler.md)
- [Acuity Scheduling API vs YouCanBookMe API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.md)
- [Aurinko Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.md)
- [Cal.com API v2 + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.md)
- [Calendly API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.md)
- [Cronofy API vs YouCanBookMe API](https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.md)
- [Nylas Calendar and Scheduler API vs YouCanBookMe API](https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.md)
- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)
- [YouCanBookMe API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.md)
- [Apiroc Unified Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.md)
- [Microsoft Graph Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp