Get an audit

Head to head · Calendar access · October 2026 research run

Aurinko Calendar API vs Zoom Scheduler API

Zoom Scheduler API scores 50.6 (D) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 4 of 7 scored categories. Aurinko Calendar API leads on schema & documentation, agent ergonomics and payments & pricing. Both do calendar access.

Best calendar and scheduling APIs for AI agents · All 45 scheduling comparisons

Aurinko Calendar APIYoxel, Inc. · HTTP API E45.6/100#861 of 950 Zoom Scheduler APIZoom Communications, Inc. · HTTP API D50.6/100#767 of 950

Which one, for what

Aurinko Calendar API E

Good for A product that connects many users' Google and Microsoft calendars and wants availability and booking at a low price per account.

Ahead on

  • Schema & documentation, 66 against 61
  • Agent ergonomics, 56 against 43
  • Payments & pricing, 40 against 25

Watch for

No status page, incident history or SLA found, and the terms supply the service as is

Zoom Scheduler API D

Good for An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.

Ahead on

  • Reliability, 63 against 40
  • Security & auth, 54 against 41
  • Maintenance & community, 28 against 20
  • Transparency & trust, 69 against 44

Watch 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

Score by category

CategoryWeight this runAurinko Calendar APIZoom Scheduler APIEdge
Reliability16%204063Zoom Scheduler API +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26661Aurinko Calendar API +5
Agent ergonomics13%16.25643Aurinko Calendar API +13
Security & auth14%17.54154Zoom Scheduler API +13
Payments & pricing10%12.54025Aurinko Calendar API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82028Zoom Scheduler API +8
Transparency & trust7%8.84469Zoom Scheduler API +25
Negative events≤1500
Total45.6 · E50.6 · D

Facts side by side

FactAurinko Calendar APIZoom Scheduler API
KindHTTP APIHTTP API
VendorYoxel, Inc.Zoom Communications, Inc.
Hosted endpointhttps://api.aurinko.iohttps://api.zoom.us/v2
TransportsHTTPHTTP
AuthOAuthOAuth
PricingPaidPaid
x402nono
LicenceProprietary service under Yoxel's Terms of Services AgreementProprietary service under the Zoom API Licence and Terms of Use
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-08-17
Terms last updated2022-08-112025-07-16
Privacy policy last updated2022-08-112026-09-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes

Verdicts

Aurinko Calendar API

A public OpenAPI 3.0 spec covers 154 operations, with free/busy, meeting-time suggestion and booking profiles alongside calendar reads and writes, and prices start at $1 an active account a month. No status page, SLA, changelog or official SDK was found, and the application's client secret reaches every connected account.

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.

Before you call either

Aurinko Calendar API

  1. Use https://api.aurinko.io/v1. Several cURL examples in the docs print https:/api.aurinko.io with one slash
  2. Send If-Match with the event's etag on PATCH /v1/calendars/{calendarId}/events/{eventId}. A stale value returns 412
  3. Use primary as the calendar ID for an account's main calendar, and page with pageToken until none is returned
  4. Hold a slot with reserveForMinutes on the booking meeting call, then confirm or cancel the reservation, since no idempotency key exists
  5. Retry 429, 408 and 5xx with exponential backoff. Do not retry 404. A 429 can come from Google or Microsoft limits behind the API

Zoom Scheduler API

  1. Call GET /scheduler/schedules/{scheduleId}/available_times and book only a spot whose status is available
  2. Send start_date_time in ISO 8601 with the booker's IANA time_zone to POST /scheduler/attendee. Expect 409 on a conflict
  3. To move a booking, cancel it with PATCH /scheduler/events/{eventId} and status set to cancelled, then book the new slot
  4. List scheduled events before retrying a booking, because no idempotency key is documented
  5. Request a new Server-to-Server OAuth token every hour. That grant issues no refresh token

Questions

Which is better for AI agents, Aurinko Calendar API or Zoom Scheduler API?

Zoom Scheduler API scores 50.6 (D) on agent readiness against Aurinko Calendar API's 45.6 (E), and leads in 4 of 7 scored categories. Aurinko Calendar API leads on schema & documentation, agent ergonomics and payments & pricing.

Do Aurinko Calendar API and Zoom Scheduler API need an API key?

Both use an OAuth sign-in.

Can an agent call Aurinko Calendar API and Zoom Scheduler API without installing anything?

Yes. Aurinko Calendar API has a hosted endpoint at https://api.aurinko.io and Zoom Scheduler API at https://api.zoom.us/v2.

Other comparisons with Aurinko Calendar API or Zoom Scheduler API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report