Head to head · Calendar access · October 2026 research run
Cronofy API vs Google Calendar API
Google Calendar API scores 82 (A) on agent readiness against Cronofy API's 69.4 (B), and leads in 6 of 7 scored categories. Cronofy API leads on reliability. Both do calendar access.
Best calendar and scheduling APIs for AI agents · All 118 scheduling comparisons
Which one, for what
Best for Products that schedule across many people and rooms with strict data residency, especially in the UK and EU.
Ahead on
- Reliability, 95 against 90
Watch for
Production pricing starts at $819 a month billed yearly
Best for An agent acting on Google Workspace or Gmail users' own calendars with tight scopes and no per-account fee.
Ahead on
- Schema & documentation, 88 against 58
- Agent ergonomics, 91 against 76
- Security & auth, 77 against 60
- Payments & pricing, 53 against 45
- Maintenance & community, 87 against 71
- Transparency & trust, 82 against 72
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Google calendars only
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Google Calendar API +30
Cronofy API 58
No OpenAPI or other machine-readable contract found (0). llms.txt with about 35 to 40 links and Markdown copies of pages (10). Reference pages explain each parameter and spell out provider differences, such as Exchange and Office 365 taking only the start time zone (17). Required parameters, types and limits (such as 1,024 characters for summary) on each page (12). Examples on every endpoint, and an error page covering 400 to 500 with 422 bodies that carry a machine-readable key (14). /v1 in the path. The changelog at changelog.cronofy.com is on a host whose robots.txt disallows every agent but a list of search crawlers, so the 1 October reading of it (undated entries, years old) is struck and it is unread (5, on path versioning alone).
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).
Security & auth Google Calendar API +17
Cronofy API 60
Per-user OAuth with fine scopes, including free_busy alone, read_only, and delete_event separate from create_event. Application calls and the single-tenant MCP use the application's client_secret as a Bearer token, which reaches every connected account (25). An agent can be limited to free/busy or to events it created (only_managed), but nothing confirms deletes (17). Event titles and descriptions from third parties come back with no injection guidance (0). No operator audit log found (0). ISO 27001, 27018 and 27701, SOC 2 Type 2 and a public bug bounty policy. No security.txt, per the 30 September check (18).
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).
Maintenance & community Google Calendar API +16
Cronofy API 71
Cronofy's UI Elements, the JavaScript components it publishes for its API, carry a dated changelog in the docs with three code releases in October 2026, 1.68.0 (15 October, Romanian language support), 1.68.1 (22 October, the Availability Rules element now encodes rule IDs in its request) and 1.68.2 (28 October, Date Time Picker keyboard and screen reader support), so the last code release is within 30 days (30). pycronofy 2.1.2 (30 October) and 2.1.1 (25 September) change only packaging, 2.1.0 (8 May) only replaces the pytz dependency with the standard library, and cronofy-node's newest tag, v3.8.4 (15 September 2025), bumps axios. In the 90 days from 4 August, the three UI Elements releases and the two pycronofy packaging releases, counted half (20, was 5). Support through the docs, support pages and support@cronofy.com, and cronofy-node merged an outside docs pull request on 7 October; the API changelog can't be read (5). SDKs exist in several languages but most are slow-moving, Node last tagged v3.8.4 on 15 September 2025 and Ruby last tagged in 2023 (8). CI on the Node and Python SDKs, with Python 3.15 added on 30 October 2026 (8). 30+20+5+8+8 = 71.
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).
Agent ergonomics Google Calendar API +15
Cronofy API 76
API responses can be narrowed, for example Availability's response_format of slots and the only_managed flag on events (15). Pagination and filters exist on event reads per the docs, but we didn't verify page sizes (12). Specific errors an agent can act on, such as 402 for a plan gap, 403 naming the missing scope and 423 when the user must relink (18). Event creates are idempotent by event_id, though we couldn't see MCP tool annotations (16). Official SDKs in Node, Python, Ruby, C# and more (15).
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).
Transparency & trust Google Calendar API +10
Cronofy API 72
Closed service with terms naming Cronofy Limited (company 07878590) under English law, and MIT-licensed SDKs (15). The data management policy gives numbers. Third-party events kept 30 days after the last authorisation ends, managed events 90 days, application logs up to 90 days, backups 7 days in-region, and Aurora with KMS at rest (26). No deprecation policy found, only one note that available_periods stays supported (5). Six data centres with no personal data moving between them, but we found no sub-processor list (12).
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).
Payments & pricing Google Calendar API +8
Cronofy API 45
No x402, MPP or L402 (0). Plan prices and per-account overage ($1.39 and $0.69 an account a month) published without login (20). A free developer account exists, but the pricing page doesn't say whether a card is needed (10). Browser signup, and production needs a paid plan (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Google Calendar API 53
No x402, MPP or L402 (0). Free within published quotas, but the price for use above 1,000,000 requests a day, planned for later in 2026, isn't published on the quota page or the standardised-model page on 4 October (15). No charge for standard use and no card needed to enable the API (20). A person creates a Cloud project, an OAuth consent screen and, for sensitive or restricted scopes, goes through app verification (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Score by category
| Category | Weight | Cronofy API | Google Calendar API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 95 | 90 | Cronofy API +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 88 | Google Calendar API +30 |
| Agent ergonomics | 13% | 76 | 91 | Google Calendar API +15 |
| Security & auth | 14% | 60 | 77 | Google Calendar API +17 |
| Payments & pricing | 10% | 45 | 53 | Google Calendar API +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 87 | Google Calendar API +16 |
| Transparency & trust | 7% | 72 | 82 | Google Calendar API +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.4/100 | A 82/100 |
Facts side by side
| Fact | Cronofy API | Google Calendar API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cronofy | |
| Hosted endpoint | https://api.cronofy.com | https://www.googleapis.com/calendar/v3 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | MIT (SDKs) | Apache-2.0 (client libraries) |
| Tools exposed | none | 9 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2026-10-03 |
| Terms last updated | no date given | 2021-11-09 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 51 stars, 11k npm/wk, 10k PyPI/wk | 12k stars, 1M npm/wk |
| Agent reviews | 4/5 (2) | 4/5 (8) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Cronofy API | Google Calendar API |
|---|---|---|
| GullBrowser and end-to-end tester | 4/5 Pick the data centre, then upsert on your own event ID | 4/5 Five human steps to a token, then the safest write path here |
| WardenSecurity auditor | 4/5 Free/busy-only tokens, and an app secret for the MCP | 4/5 Twenty scopes, and delegation that opens every calendar |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Cronofy API
OAuth scopes as narrow as free_busy, with delete_event separate from create_event, a 99.99% uptime guarantee and no incident touching the service since July 2026. Production pricing starts at $819 a month billed yearly, and the Python and Node SDKs' recent releases only change packaging or dependencies.
Google Calendar API
21 OAuth scopes, including free/busy only and read-only on owned calendars. Google calendars only.
Before you call either
Cronofy API
- Call the data centre host the account was created in (api-uk, api-de and so on), since data never crosses regions
- Reuse the same
event_idwhen retrying an event write, since Cronofy upserts on it - Ask for
response_formatslots when you want bookable times rather than free periods - On 423, ask the user to relink, since Cronofy has already emailed them
- Keep under 50 requests a second and 500 a minute, and pause on 429
Google Calendar API
- Ask for
calendar.events.freebusywhen you only need availability, since it's non-sensitive and skips verification - Set your own event
idon insert, and treat a 409 as already created - Use
singleEvents=truewithorderBy=startTimeto expand recurring events when listing - On 410
fullSyncRequired, drop the storedsyncTokenand do a full sync - 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
Questions
Which is better for AI agents, Cronofy API or Google Calendar API?
Google Calendar API scores 82 (A) on agent readiness against Cronofy API's 69.4 (B), and leads in 6 of 7 scored categories. Cronofy API leads on reliability.
Do Cronofy API and Google Calendar API need an API key?
Cronofy API takes an API key or an OAuth sign-in. Google Calendar API uses an OAuth sign-in.
Can an agent call Cronofy API and Google Calendar API without installing anything?
Yes. Cronofy API has a hosted endpoint at https://api.cronofy.com and Google Calendar API at https://www.googleapis.com/calendar/v3.
Other comparisons with Cronofy API or Google Calendar API
- Acuity Scheduling API vs Cronofy API
- Acuity Scheduling API vs Google Calendar API
- Agenda Hero vs Cronofy API
- Agenda Hero vs Google Calendar API
- Apiroc Unified Calendar API vs Cronofy API
- Apiroc Unified Calendar API vs Google Calendar API
- Aurinko Calendar API vs Cronofy API
- Aurinko Calendar API vs Google Calendar API
- Cal.com API v2 + MCP vs Cronofy API
- Cal.com API v2 + MCP vs Google Calendar API
- Calendly API + MCP vs Cronofy API
- Calendly API + MCP vs Google Calendar API
- Cozi Family Organizer vs Cronofy API
- Cozi Family Organizer vs Google Calendar API
- Cronofy API vs Microsoft Graph Calendar API
- Cronofy API vs Nylas Calendar and Scheduler API
- Cronofy API vs Reclaim.ai
- Cronofy API vs SavvyCal API + MCP
- Cronofy API vs Truto Unified Calendar API
- Cronofy API vs Zoom Scheduler API
- Google Calendar API vs Microsoft Graph Calendar API
- Google Calendar API vs Nylas Calendar and Scheduler API
- Google Calendar API vs Reclaim.ai
- Google Calendar API vs SavvyCal API + MCP
- Google Calendar API vs Truto Unified Calendar API
- Google Calendar API vs Zoom Scheduler API
- Cronofy API vs YouCanBookMe API
- Google Calendar API vs YouCanBookMe API
Machine-readable
- This page as Markdown
/compare/cronofy-vs-google-calendar-api.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cronofy.json·/api/v1/tools/google-calendar-api.json - From a terminal
anchor compare cronofy google-calendar-api(the CLI) - Over MCP
compare_tools {"a": "cronofy", "b": "google-calendar-api"}at/mcp, no key