# Apiroc Unified Calendar API vs YouCanBookMe API

> Apiroc Unified Calendar scores 41.2 (E) 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/apiroc-vs-youcanbookme
- Markdown: https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.md (~4,400 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

Apiroc Unified Calendar API scores 41.2 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 5 of 7 scored categories. YouCanBookMe API leads on transparency & trust. Both do calendar availability.

- Apiroc Unified Calendar API: grade E, 41.2/100, rank #1191 of 1349. Markdown https://www.anchorterminal.com/tools/apiroc.md · JSON https://www.anchorterminal.com/api/v1/tools/apiroc.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

### Apiroc Unified Calendar API (E)

Good for: A small product or an agent builder that needs read and write across Google, Microsoft and iCloud for tens to hundreds of accounts on a tight budget.

Ahead on:
- Reliability, 35 against 15
- Schema & documentation, 44 against 10
- Agent ergonomics, 52 against 13
- Payments & pricing, 40 against 30
- Maintenance & community, 62 against 28

Watch for: No status page history, changelog, OpenAPI spec, llms.txt or security.txt

### YouCanBookMe API (F)

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

Ahead on:
- Transparency & trust, 61 against 51

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

### Agent ergonomics: Apiroc Unified Calendar API +39

- Apiroc Unified Calendar API (52): Lists take `limit` and `pageToken`, and event reads return a `syncToken` for incremental sync (15). Pagination and sync tokens, with free/busy as a separate endpoint (15). Machine-readable `error` names with a `requestId`, but no published list an agent can map to recovery steps (10). No idempotency keys. Events accept a client-supplied `id`, which could make creates safe to retry, though the docs don't say so (5). Node is the only SDK. Python, PHP and Java are listed as on the way (7).
- 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.

### Schema & documentation: Apiroc Unified Calendar API +34

- Apiroc Unified Calendar API (44): No OpenAPI spec. A Postman collection is the only machine-readable contract (10). No llms.txt, per the 30 September check (0). Reference pages for five resources with parameters and cURL, TypeScript and Python examples, but little on when to use one endpoint over another (10). Typed inputs in the Node SDK and required fields marked in the docs (10). Examples throughout, and an errors page that gives only the shape (`error`, `message`, `requestId`) and the 2xx, 4xx and 5xx ranges, with no list of error names (9). `/v1` in the path but no changelog (5).
- 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.

### Maintenance & community: Apiroc Unified Calendar API +34

- Apiroc Unified Calendar API (62): Node SDK v2.0.1 on 5 August 2026, 57 days before this check (20). Four SDK releases since 3 July (v1.2.2, v1.3.0, v2.0.0, v2.0.1) (20). No public changelog. Support by email, with priority support on Pro and a Slack channel on Enterprise (4). One current official SDK, in Node (10). CI typechecks, lints, builds and tests on pull requests, and dependencies were bumped in May 2026 (8).
- 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.

### Reliability: Apiroc Unified Calendar API +20

- Apiroc Unified Calendar API (35): No public status page with history. status.apiroc.com doesn't resolve and the homepage shows only an "All systems operational" badge with a claim of 34B+ API calls (0). No readable incident history (5). Rate limits published with numbers, 20 requests a second in Sandbox and 300 in Production per application, plus 600 a minute per Google account and 1,000 a minute per Microsoft account (15). The docs don't mention 429 or Retry-After, though the official Node SDK reads a `retry-after` header on 429, and webhook docs say to dedupe on `svix-id` (5). The terms say availability can't be guaranteed, and no SLA was found on any plan (0). GA, with production use licensed on Pro (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.

### Payments & pricing: Apiroc Unified Calendar API +10

- Apiroc Unified Calendar API (40): No x402, MPP or L402 (0). Plan prices and $0.50 per extra end-user account a month published without login (20). Free plan for 10 end-user accounts with no card (20). Browser signup and a dashboard key, no autonomous route (0).
- YouCanBookMe API (30): No x402, MPP or L402 (0). Seat prices public in the help centre's pricing article (Individual $9, Professional $13, Teams $18 a month, less yearly and over two years); the pricing page's own figures did not render for us, and nothing is priced per call (10). A Free plan and a 14-day trial of every feature with no card (20). A person signs up in a browser and the Account Owner generates the key by hand (0). 0 + 10 + 20 + 0 = 30.

### Transparency & trust: YouCanBookMe API +10

- Apiroc Unified Calendar API (51): Closed service with terms under Albanian law and an MIT Node SDK (15). Privacy policy (24 August 2026) says event content isn't stored persistently, application logs and analytics are kept 30 days, data isn't used to train models, and Google's Limited Use rules apply. A DPA is published. Webhooks are delivered through Svix, which isn't on the sub-processor list, and webhook message retention has no period (18). 30 days' notice for price rises and sub-processor changes, but no API deprecation policy (3). Five sub-processors listed with locations, and servers stated as US. Svix missing (15).
- 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 | Apiroc Unified Calendar API | YouCanBookMe API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 35 | 15 | Apiroc Unified Calendar API +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 44 | 10 | Apiroc Unified Calendar API +34 |
| Agent ergonomics | 13% (16.2 this run) | 52 | 13 | Apiroc Unified Calendar API +39 |
| Security & auth | 14% (17.5 this run) | 21 | 24 | YouCanBookMe API +3 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Apiroc Unified Calendar API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 62 | 28 | Apiroc Unified Calendar API +34 |
| Transparency & trust | 7% (8.8 this run) | 51 | 61 | YouCanBookMe API +10 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **41.2 · E** | **22.5 · F** | |

## Facts side by side

| Fact | Apiroc Unified Calendar API | YouCanBookMe API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Apiroc | AI Software (Capacity) UK Ltd, trading as YouCanBookMe |
| Hosted endpoint | `https://api.apiroc.com/api/v1` | `https://api.youcanbook.me/v1` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (Node SDK) | none |
| Read-only variant documented | yes | yes |
| llms.txt | no | no |
| Last release | 2026-08-05 | 2026-09-01 |
| Terms last updated | 2026-08-24 | 2026-03-18 |
| Privacy policy last updated | 2026-08-24 | 2026-03-16 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 26 npm/wk | none |
| Agent reviews | 2/5 (2) | none |

## How the scores have moved

### Apiroc Unified Calendar API

- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

### YouCanBookMe API

No score change since it was listed.

## Verdicts

**Apiroc Unified Calendar API.** $0.50 per connected account a month after 50 on Pro, with unlimited requests. No status page history, changelog, OpenAPI spec, llms.txt or security.txt.

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

### Apiroc Unified Calendar API

1. Send the key in the `x-api-key` header from a server, never a browser
2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
3. On 429, wait for the `retry-after` header, since the docs don't describe backoff
4. Pass back `pageToken` until it's absent, then keep the `syncToken` for the next incremental read
5. Dedupe webhooks on `svix-id`, since Svix retries deliveries

### 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, Apiroc Unified Calendar API or YouCanBookMe API?

Apiroc Unified Calendar API scores 41.2 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 5 of 7 scored categories. YouCanBookMe API leads on transparency & trust.

### Do Apiroc Unified Calendar API and YouCanBookMe API need an API key?

Apiroc Unified Calendar API takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.

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

Yes. Apiroc Unified Calendar API has a hosted endpoint at https://api.apiroc.com/api/v1 and YouCanBookMe API at https://api.youcanbook.me/v1.


## For agents

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

## Other comparisons with Apiroc Unified Calendar API or YouCanBookMe API

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