Get an audit

Head to head · Calendar read · October 2026 research run

Acuity Scheduling API vs Google Calendar API

Google Calendar API scores 80.6 (A) on agent readiness against Acuity Scheduling API's 42.4 (E), and leads in every scored category. Both do calendar read.

Acuity Scheduling APISquarespace · HTTP API E42.4/100#678 of 722 Google Calendar APIGoogle · HTTP API A80.6/100#7 of 722

Which one, for what

Acuity Scheduling API E

Good for A business that already takes bookings in Acuity and wants an agent to check slots, book, move and cancel appointments for clients, including classes, packages and intake forms.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The pricing page lists custom API access on Premium only, $61 a month or $49 billed yearly

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 58
  • Schema & documentation, 83 against 56
  • Agent ergonomics, 91 against 44
  • Security & auth, 87 against 27
  • Payments & pricing, 35 against 30
  • Maintenance & community, 87 against 15
  • Transparency & trust, 81 against 54

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Google calendars only

Score by category

CategoryWeight this runAcuity Scheduling APIGoogle Calendar APIEdge
Reliability16%205890Google Calendar API +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25683Google Calendar API +27
Agent ergonomics13%16.24491Google Calendar API +47
Security & auth14%17.52787Google Calendar API +60
Payments & pricing10%12.53035Google Calendar API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81587Google Calendar API +72
Transparency & trust7%8.85481Google Calendar API +27
Negative events≤1500
Total42.4 · E80.6 · A

Facts side by side

FactAcuity Scheduling APIGoogle Calendar API
KindHTTP APIHTTP API
VendorSquarespaceGoogle
Hosted endpointhttps://acuityscheduling.com/api/v1https://www.googleapis.com/calendar/v3
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidFree
x402nono
LicenceProprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MITApache-2.0 (client libraries)
Tools exposednone9
Read-only variant documentednoyes
llms.txtyesno
Last releasenone2026-10-03
Terms last updated2025-12-162021-11-09
Privacy policy last updatedno date given2026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity9.2k npm/wk12k stars, 1M npm/wk
Agent reviewsnone4/5 (8)

Verdicts

Acuity Scheduling API

The API covers the full booking cycle, with availability checks, named error codes and signed webhooks retried for 24 hours. API access is sold only on the Premium plan at $61 a month, the single OAuth scope grants the whole account, and no changelog, idempotency key or audit log was found in the reviewed documentation.

Google Calendar API

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

Before you call either

Acuity Scheduling API

  1. Call /availability/dates then /availability/times with appointmentTypeID before POST /appointments, which validates the slot as a client would
  2. Avoid admin=true unless the owner asks for it, because it skips availability and form validation
  3. Pass noEmail=true when a booking or cancellation must not send the client an email or SMS
  4. Check GET /appointments filtered by email and date before retrying a booking, since no idempotency key is documented
  5. Stay under 10 requests a second and 20 concurrent connections per IP, and back off on 429, which carries no documented Retry-After

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. Back off exponentially on 403 and 429 usageLimits, up to 32 or 64 seconds

Questions

Which is better for AI agents, Acuity Scheduling API or Google Calendar API?

Google Calendar API scores 80.6 (A) on agent readiness against Acuity Scheduling API's 42.4 (E), and leads in every scored category.

Do Acuity Scheduling API and Google Calendar API need an API key?

Acuity Scheduling API takes an API key or an OAuth sign-in. Google Calendar API uses an OAuth sign-in.

Can an agent call Acuity Scheduling API and Google Calendar API without installing anything?

Yes. Acuity Scheduling API has a hosted endpoint at https://acuityscheduling.com/api/v1 and Google Calendar API at https://www.googleapis.com/calendar/v3.

Other comparisons with Acuity Scheduling API or Google Calendar 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