{ "data": { "a": { "slug": "acuity-scheduling", "name": "Acuity Scheduling API", "vendor": "Squarespace", "vendorUrl": "https://acuityscheduling.com", "kind": "http-api", "category": "scheduling", "summary": "Acuity Scheduling is Squarespace's appointment booking product. Its REST API reads availability, creates, reschedules and cancels appointments, manages clients and blocked time, and sends webhooks, with Basic authentication or OAuth2.", "url": "https://www.anchorterminal.com/tools/acuity-scheduling", "markdownUrl": "https://www.anchorterminal.com/tools/acuity-scheduling.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/acuity-scheduling.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/acuity-scheduling.json", "dns": "acuity-scheduling.grade.anchorterminal.com", "repo": "https://github.com/AcuityScheduling/acuity-js", "license": "Proprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MIT", "transports": [ "http" ], "remoteUrl": "https://acuityscheduling.com/api/v1", "packages": [ { "registry": "npm", "name": "acuityscheduling" } ], "auth": "mixed", "authNotes": "Self-serve. One account uses HTTP Basic authentication with the numeric User ID as username and the account API key as password, found under Integrations in the Acuity settings. Apps that connect other people's accounts register an OAuth2 client at https://acuityscheduling.com/oauth2/register and use the authorisation code grant, which has one scope, `api-v1`, and returns a Bearer token. `POST /oauth2/disconnect` disables a token. No app review step, token expiry or refresh token is described in the OAuth guide. Requests must come from a server, as cross-origin requests are refused.", "pricing": "paid", "pricingNotes": "The pricing page lists \"Custom API and CSS\" on the Premium plan only, at $61 a month or $49 a month billed yearly. Starter is $20 ($16 yearly) and Standard $34 ($27 yearly), in USD before tax. Each plan has a 7-day trial with no card needed. We did not establish whether the trial includes API access. No free tier or sandbox was found, and API calls carry no separate charge. An Enterprise plan with additional APIs is sold through sales (https://acuityscheduling.com/pricing).", "priceSummary": "$61 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs or on the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 9182, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.acuityscheduling.com", "llmsTxt": "https://developers.acuityscheduling.com/llms.txt", "capabilities": [ "calendar.read", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "paid", "trial", "rest", "oauth", "basic-auth", "webhooks", "llms-txt", "closed-source", "status-page", "hipaa", "nodejs", "php" ], "graded": true, "anchor": { "graded": true, "score": 42.5, "grade": "E", "agentReady": false, "rank": 1169, "ranked": true, "rankOf": 1349, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 44, "maintenance": 15, "payments": 30, "reliability": 58, "schema": 56, "security": 27, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Availability by date and time, booking, rescheduling and cancelling are separate documented endpoints under `/api/v1`", "Errors return a status code, a named `error` code and a message, and a 404 suggests the nearest valid path", "Webhooks are signed with HMAC-SHA256 in `x-acuity-signature` and retried nine times over 24 hours", "Every docs page has a Markdown copy with an OpenAPI 3.1 fragment, and `llms.txt` is published", "Rate limit stated as 10 requests a second and 20 concurrent connections per IP" ], "weaknesses": [ "The pricing page lists custom API access on Premium only, $61 a month or $49 billed yearly", "OAuth2 has one scope, `api-v1`, and Basic authentication uses one account API key, so no read-only credential exists", "No changelog or deprecation policy was found, and the Developer Terms allow changes without notice", "The Node.js and PHP SDKs were last released in July 2019", "The status page records two critical service disruptions in the last 90 days, on 19 July and 12 August 2026" ], "agentNotes": [ "Call `/availability/dates` then `/availability/times` with `appointmentTypeID` before `POST /appointments`, which validates the slot as a client would", "Avoid `admin=true` unless the owner asks for it, because it skips availability and form validation", "Pass `noEmail=true` when a booking or cancellation must not send the client an email or SMS", "Check `GET /appointments` filtered by `email` and date before retrying a booking, since no idempotency key is documented", "Stay under 10 requests a second and 20 concurrent connections per IP, and back off on 429, which carries no documented `Retry-After`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.5 } ], "editorialScores": { "ergonomics": 44, "maintenance": 15, "payments": 30, "reliability": 58, "schema": 56, "security": 27, "transparency": 34 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-10-08", "maintenance": "2026-10-08", "payments": "2026-10-08", "reliability": "2026-10-08", "schema": "2026-10-08", "security": "2026-10-08", "transparency": "2026-10-08" }, "last": "2026-10-08", "lastMoved": "2026-10-28", "oldest": "2026-10-08", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install --save acuityscheduling", "http": "curl -u ACUITY_USER_ID:ACUITY_API_KEY \"https://acuityscheduling.com/api/v1/appointments\"" }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/acuity-scheduling" }, "area": "everyday", "unitPrices": [ { "item": "Premium (the plan with API access)", "unit": "month", "usd": 61, "note": "Monthly billing. $49 a month billed yearly" } ], "provenance": { "legalEntity": "Squarespace, Inc.", "domain": "acuityscheduling.com", "domainRegistered": "2007-01-15", "endpointOnVendorDomain": true, "terms": "https://www.squarespace.com/developer-terms", "privacy": "https://www.squarespace.com/privacy", "statusPage": "https://status.acuityscheduling.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The developer docs' legal page links two documents, Squarespace's Developer Terms (last updated 16 December 2025) and Squarespace's privacy policy (effective 15 July 2026). Both name acuityscheduling.com.", "The contracting entity is Squarespace, Inc., 225 Varick Street, New York, for US users and Squarespace Ireland Limited, Dublin, for others.", "acuityscheduling.com/.well-known/security.txt returns 404. www.squarespace.com publishes one that expires on 1 January 2028 and points to its vulnerability reporting page.", "The API answers at https://acuityscheduling.com/api/v1 and OAuth at https://acuityscheduling.com/oauth2.", "RDAP gives a registration date of 2007-01-15 and MarkMonitor Inc. as registrar.", "No changelog was found. developers.acuityscheduling.com/changelog.md returns the docs' not-found page." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/acuity-scheduling.json", "live": { "slug": "acuity-scheduling", "probe": { "target": "https://acuityscheduling.com/api/v1", "method": "get", "lastAt": "2026-11-04T22:02:23.224247677Z", "lastOk": true, "lastStatus": 404, "lastMs": 457, "authRequired": false, "uptime24h": 100, "uptime30d": 99.45, "p50ms24h": 493, "p95ms24h": 563, "samples24h": 247, "samples30d": 6788, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 218 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 246 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 227, "ok": 227 } ], "outages": [ { "start": "2026-10-21T13:56:25.331686093Z", "end": "2026-10-21T17:02:44.771636572Z", "note": "HTTP 503 server error" } ] }, "vendorStatus": { "page": "https://status.acuityscheduling.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T22:00:15.34626941Z" }, "versions": [ { "registry": "npm", "name": "acuityscheduling", "version": "0.1.9", "seenAt": "2026-11-04T19:54:18.628929818Z" } ], "githubStars": 37, "npmWeekly": 23672, "securityTxt": { "url": "https://acuityscheduling.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:25.404739098Z" }, "llmsTxt": { "url": "https://developers.acuityscheduling.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:21:40.217009029Z" }, "domain": { "domain": "acuityscheduling.com", "registered": "2007-01-15", "source": "https://rdap.verisign.com/com/v1/domain/acuityscheduling.com", "checkedAt": "2026-11-01T14:27:00.066842758Z" }, "pages": [ { "url": "https://acuityscheduling.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:14:17.867025485Z", "changedAt": "2026-10-14T20:34:38.321757155Z", "fingerprint": "f06a7932ca32" }, { "url": "https://www.squarespace.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:45:49.564240945Z", "changedAt": "2026-10-24T02:36:55.582176904Z", "fingerprint": "35717e2f2fed" }, { "url": "https://www.squarespace.com/developer-terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:45:47.029655517Z", "changedAt": "2026-10-24T02:36:53.092977407Z", "fingerprint": "4eae8f3ec295" } ], "github": { "repo": "acuityscheduling/acuity-js", "checkedAt": "2026-11-02T08:27:56.255789894Z", "stars": 37, "archived": false, "issuesEnabled": true, "pushedAt": "2019-08-16T08:52:10Z", "openIssues": 1, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 9, "unanswered": 1, "medianDays": 4.4 } }, "updatedAt": "2026-11-04T22:02:23.224247677Z" } }, "answer": "Acuity Scheduling API scores 42.5 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 4 of 7 scored categories. YouCanBookMe API leads on maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "youcanbookme", "name": "YouCanBookMe API", "vendor": "AI Software (Capacity) UK Ltd, trading as YouCanBookMe", "vendorUrl": "https://youcanbook.me", "kind": "http-api", "category": "scheduling", "summary": "YouCanBookMe is a booking-page service from the UK company of the same name, owned by Capacity since 2025. Its REST API manages account details, booking pages (profiles) and bookings over HTTP Basic auth, with webhooks from booking notifications.", "url": "https://www.anchorterminal.com/tools/youcanbookme", "markdownUrl": "https://www.anchorterminal.com/tools/youcanbookme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/youcanbookme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/youcanbookme.json", "dns": "youcanbookme.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.youcanbook.me/v1", "packages": [], "auth": "api-key", "authNotes": "HTTP Basic authentication with the account email address or account ID as the username and an account API key as the password. Only the Account Owner can generate, view, copy or delete the key, under Account Password \u0026 Security \u003e Authentication and API, and the help centre says the API key is available on the Team plan. No scopes, expiry or per-user keys are described. Administrators and Contributors must ask the owner for the key.", "pricing": "freemium", "pricingNotes": "Free plan with 1 calendar, 1 booking page and 30 bookings a month, with YouCanBookMe branding. Individual $9, Professional $13 and Teams $18 a seat a month, with 10 per cent off yearly and 20 per cent off for two years ($7.20, $10.40 and $14.40), per the help centre's pricing article. 14-day trial of every feature with no card, per the pricing page. API access is listed under the Team plan; webhooks need Professional or Teams.", "priceSummary": "$9 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, in the help centre API and webhook articles or in the API's error response (checked 2026-11-03). The API reference itself could not be read.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://ycbm.stoplight.io/", "capabilities": [ "calendar.booking", "calendar.availability", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "free-trial", "no-card", "api-key", "webhooks", "soc2", "iso27001", "uk", "closed-source" ], "lastRelease": "2026-09-01", "graded": true, "anchor": { "graded": true, "score": 22.5, "grade": "F", "agentReady": false, "rank": 1286, "ranked": true, "rankOf": 1349, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 13, "maintenance": 28, "payments": 30, "reliability": 15, "schema": 10, "security": 24, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "A booking-page product for small businesses, closest to calendly and savvycal in scheduling.", "strengths": [ "SOC 2 Type II and ISO/IEC 27001:2022 (certificate issued 20 February 2024) listed on the security page, with AES-256 at rest on AWS", "Free plan and a 14-day trial of every feature with no card", "Privacy notice (16 March 2026) states retention periods, 24 months for booking data by default, and says booking data is not used to train AI models", "Webhook notifications on six booking triggers with a JSON payload the user shapes, on Professional and Teams", "The API answers with a JSON error envelope carrying a code, message and status, and declares its version in an `x-api-version` header" ], "weaknesses": [ "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", "One account-wide API key over HTTP Basic auth, created only by the Account Owner, with no scopes or expiry documented", "API access is listed only on the Team plan ($18 a seat a month)", "No rate limits, 429 handling, idempotency keys, OpenAPI file, llms.txt or official SDK were found", "No security.txt, bug bounty or disclosure policy, and the status page at youcanbookmestatus.com did not resolve for us" ], "agentNotes": [ "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", "Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us", "Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented", "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", "Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 22.5 } ], "editorialScores": { "ergonomics": 13, "maintenance": 28, "payments": 30, "reliability": 15, "schema": 10, "security": 24, "transparency": 52 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -u \"$YCBM_ACCOUNT_ID:$YCBM_API_KEY\" https://api.youcanbook.me/v1/profiles" }, "letme": { "capability": "https://letme.dev/calendar.booking", "tool": "https://letme.dev/youcanbookme" }, "area": "everyday", "unitPrices": [ { "item": "Individual", "unit": "seat-month", "usd": 9, "note": "$8.10 a month yearly, $7.20 over two years, per the help centre" }, { "item": "Professional", "unit": "seat-month", "usd": 13, "note": "$11.70 a month yearly, $10.40 over two years" }, { "item": "Teams", "unit": "seat-month", "usd": 18, "note": "Per seat. $16.20 yearly, $14.40 over two years. The plan that lists API access" } ], "provenance": { "legalEntity": "AI Software (Capacity) UK Ltd", "domain": "youcanbook.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://youcanbook.me/terms", "privacy": "https://youcanbook.me/privacy", "statusPage": "https://www.youcanbookmestatus.com", "changelog": "https://youcanbook.me/product-updates", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms (last updated 18 March 2026) name AI Software (Capacity) UK Ltd, trading as YouCanBookMe, under English law. Clause 15.3 bars data mining, robots and similar extraction tools without written consent, and clause 7.2 bars downloading the Site's software. Recorded as a fact; the public pages were read.", "The privacy notice (16 March 2026) gives company number 7221202, AWS hosting in the United States, a DPA on request through HelloSign, and retention of 24 months for booking data and up to 7 years for support messages.", "youcanbook.me/robots.txt disallows only HubSpot preview and preference paths. support.youcanbook.me/robots.txt disallows account, search and request paths; the API article there answered a Cloudflare challenge (403), which is the host's block, not a robots rule. ycbm.capacity.com and ycbm.stoplight.io allow all.", "The status page linked from youcanbook.me/help, www.youcanbookmestatus.com, did not resolve from our reader on 3 November 2026 (DNS), with or without www, so no incident history was read.", "youcanbook.me/.well-known/security.txt returns 404. The security page gives compliance@youcanbook.me as its contact.", "RDAP for youcanbook.me (rdap.nic.me) could not be reached from our shell, so the registration date is blank.", "The product updates page at youcanbook.me/product-updates is dated by month; its newest entry is September 2026 (registered SMS numbers), which lastRelease records as the first of that month." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/youcanbookme.json", "live": { "slug": "youcanbookme", "probe": { "target": "https://api.youcanbook.me/v1", "method": "get", "lastAt": "2026-11-04T22:03:06.892122606Z", "lastOk": true, "lastStatus": 400, "lastMs": 409, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 220, "p95ms24h": 447, "samples24h": 68, "samples30d": 68, "days": [ { "date": "2026-11-04", "probes": 68, "ok": 68 } ] }, "vendorStatus": { "page": "https://www.youcanbookmestatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:27:01.611847667Z" }, "securityTxt": { "url": "https://youcanbook.me/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:28.156243558Z" }, "updatedAt": "2026-11-04T22:03:06.892122606Z" } }, "edges": [ { "by": 46, "category": "schema", "leads": "acuity-scheduling", "name": "Schema \u0026 documentation", "reasons": { "a": "Each reference page carries an OpenAPI 3.1 fragment for its own operation, generated by the docs platform from hand-written pages. No single downloadable specification was found (15). `llms.txt` is published and every page has a Markdown copy, but the index lists only five of 36 reference pages (8). Pages explain client and admin booking modes and when availability is validated, without when-not-to-use guidance (10). Parameters are typed with required fields, but there are no enums and `datetime` is any string PHP's strtotime accepts (8). Request examples, an error table and per-endpoint error codes (12). The path is versioned as v1, with no changelog found (3). Total 56.", "b": "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." }, "scores": { "a": 56, "b": 10 } }, { "by": 43, "category": "reliability", "leads": "acuity-scheduling", "name": "Reliability", "reasons": { "a": "Graded as a hosted API. Statuspage site at status.acuityscheduling.com with incident history, though one component stands for the whole product (20). In the 90 days to 8 October 2026 the feed shows a critical disruption of 2 hours 5 minutes on 19 July and one of 18 minutes on 12 August, both marked as possibly affecting all users and services, plus a four-day iOS app fault and three minor integration incidents. Read as one major outage (10). 10 requests a second and 20 concurrent connections per IP (15). The 429 body is documented, with no `Retry-After`, backoff advice or idempotency key for booking writes (3). No SLA found, and the Developer Terms disclaim uninterrupted service (0). The v1 API is generally available (10). Total 58.", "b": "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." }, "scores": { "a": 58, "b": 15 } }, { "by": 31, "category": "ergonomics", "leads": "acuity-scheduling", "name": "Agent ergonomics", "reasons": { "a": "`max` caps list size and `excludeForms` trims intake forms from appointments. No field selection (10). Filters by date, calendar, type and client, but no cursor or offset is documented, so long lists need date windows (10). Errors carry a status, a named code and a message, and a 404 suggests the nearest path (16). No idempotency key or safe-retry guidance for `POST /appointments` (0). Booking needs five fields and picks a calendar when none is given. SDKs exist for Node.js and PHP, both last released in 2019 (8). Total 44.", "b": "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." }, "scores": { "a": 44, "b": 13 } }, { "by": 13, "category": "maintenance", "leads": "youcanbookme", "name": "Maintenance \u0026 community", "reasons": { "a": "No changelog or release notes found. The docs' own page dates show the OAuth guide edited on 1 October 2026 and the webhooks guide on 25 June 2026, which we count as the latest dated change (10). No three dated entries in 90 days (0). A developer email address and a support form, with no public issue tracker for the API (5). The Node.js and PHP SDKs were last tagged in July 2019 (0). No current package to assess (0). Total 15.", "b": "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." }, "scores": { "a": 15, "b": 28 } }, { "by": 6, "category": "transparency", "leads": "youcanbookme", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Squarespace's Developer Terms of 16 December 2025, with MIT SDKs (15). The privacy policy of 15 July 2026 names acuityscheduling.com and states no retention periods. The DPA of the same date promises deletion within 90 days of cancellation on written request (15). No deprecation policy, and the Developer Terms allow changes to developer tools without notice (0). Sub-processors are disclosed only on request by email, and data may move to any country where Squarespace or its sub-processors operate, the US in particular (4). Total 34.", "b": "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." }, "scores": { "a": 55, "b": 61 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Squarespace", "b": "AI Software (Capacity) UK Ltd, trading as YouCanBookMe", "name": "Vendor" }, { "a": "https://acuityscheduling.com/api/v1", "b": "https://api.youcanbook.me/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MIT", "b": "none", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "none", "b": "2026-09-01", "name": "Last release" }, { "a": "2025-12-16", "b": "2026-03-18", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-03-16", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "9.2k npm/wk", "b": "none", "name": "Popularity" }, { "a": "2.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Acuity Scheduling API scores 42.5 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 4 of 7 scored categories. YouCanBookMe API leads on maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Acuity Scheduling API or YouCanBookMe API?" }, { "answer": "Acuity Scheduling API takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.", "question": "Do Acuity Scheduling API and YouCanBookMe API need an API key?" }, { "answer": "Yes. Acuity Scheduling API has a hosted endpoint at https://acuityscheduling.com/api/v1 and YouCanBookMe API at https://api.youcanbook.me/v1.", "question": "Can an agent call Acuity Scheduling API and YouCanBookMe API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 58 against 15", "Schema \u0026 documentation, 56 against 10", "Agent ergonomics, 44 against 13" ], "also": null, "goodFor": "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.", "slug": "acuity-scheduling", "watchFor": "The pricing page lists custom API access on Premium only, $61 a month or $49 billed yearly" }, { "aheadOn": [ "Maintenance \u0026 community, 28 against 15", "Transparency \u0026 trust, 61 against 55" ], "also": [ "Free to start without a card" ], "goodFor": "A booking-page product for small businesses, closest to calendly and savvycal in scheduling.", "slug": "youcanbookme", "watchFor": "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" } ], "history": { "acuity-scheduling": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": 0, "from": 42.5, "fromGrade": "E", "to": 42.5, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 42.4, "fromGrade": "E", "to": 42.5, "toGrade": "E" } ], "youcanbookme": null }, "job": { "capability": "calendar.booking", "name": "Calendar booking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-agenda-hero.json", "title": "Acuity Scheduling API vs Agenda Hero", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-agenda-hero" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.json", "title": "Acuity Scheduling API vs Apiroc Unified Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.json", "title": "Acuity Scheduling API vs Aurinko Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cal-com.json", "title": "Acuity Scheduling API vs Cal.com API v2 + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cal-com" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly.json", "title": "Acuity Scheduling API vs Calendly API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cozi.json", "title": "Acuity Scheduling API vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy.json", "title": "Acuity Scheduling API vs Cronofy API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-google-calendar-api.json", "title": "Acuity Scheduling API vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-microsoft-graph-calendar.json", "title": "Acuity Scheduling API vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-microsoft-graph-calendar" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.json", "title": "Acuity Scheduling API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.json", "title": "Acuity Scheduling API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler.json", "title": "Acuity Scheduling API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.json", "title": "Aurinko Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.json", "title": "Cal.com API v2 + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.json", "title": "Calendly API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.json", "title": "Cronofy API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.json", "title": "Nylas Calendar and Scheduler API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.json", "title": "SavvyCal API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.json", "title": "YouCanBookMe API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.json", "title": "Apiroc Unified Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.json", "title": "Google Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.json", "title": "Microsoft Graph Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme" } ], "panel": null, "scores": [ { "acuity-scheduling": 58, "by": 43, "edge": "acuity-scheduling", "key": "reliability", "name": "Reliability", "weight": 16, "youcanbookme": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "acuity-scheduling": 56, "by": 46, "edge": "acuity-scheduling", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "youcanbookme": 10 }, { "acuity-scheduling": 44, "by": 31, "edge": "acuity-scheduling", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "youcanbookme": 13 }, { "acuity-scheduling": 27, "by": 3, "edge": "acuity-scheduling", "key": "security", "name": "Security \u0026 auth", "weight": 14, "youcanbookme": 24 }, { "acuity-scheduling": 30, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "youcanbookme": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "acuity-scheduling": 15, "by": 13, "edge": "youcanbookme", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "youcanbookme": 28 }, { "acuity-scheduling": 55, "by": 6, "edge": "youcanbookme", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "youcanbookme": 61 } ], "summary": "Acuity Scheduling API scores 42.5 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 4 of 7 scored categories. YouCanBookMe API leads on maintenance \u0026 community and transparency \u0026 trust. Both do calendar booking.", "tasks": null, "tutorials": [], "verdicts": { "acuity-scheduling": "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.", "youcanbookme": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme", "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.min.md" }, "markdown": "Acuity Scheduling API scores 42.5 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 4 of 7 scored categories. YouCanBookMe API leads on maintenance \u0026 community and transparency \u0026 trust. Both do calendar booking.\n\n- Acuity Scheduling API: grade E, 42.5/100, rank #1169 of 1349. Markdown https://www.anchorterminal.com/tools/acuity-scheduling.md · JSON https://www.anchorterminal.com/api/v1/tools/acuity-scheduling.json\n- 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\n- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md\n- All 89 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md\n\n## Which one, for what\n\n### Acuity Scheduling API (E)\n\nGood 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.\n\nAhead on:\n- Reliability, 58 against 15\n- Schema \u0026 documentation, 56 against 10\n- Agent ergonomics, 44 against 13\n\nWatch for: The pricing page lists custom API access on Premium only, $61 a month or $49 billed yearly\n\n### YouCanBookMe API (F)\n\nGood for: A booking-page product for small businesses, closest to calendly and savvycal in scheduling.\n\nAhead on:\n- Maintenance \u0026 community, 28 against 15\n- Transparency \u0026 trust, 61 against 55\n\nAlso in its favour:\n- Free to start without a card\n\nWatch 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\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Acuity Scheduling API +46\n\n- Acuity Scheduling API (56): Each reference page carries an OpenAPI 3.1 fragment for its own operation, generated by the docs platform from hand-written pages. No single downloadable specification was found (15). `llms.txt` is published and every page has a Markdown copy, but the index lists only five of 36 reference pages (8). Pages explain client and admin booking modes and when availability is validated, without when-not-to-use guidance (10). Parameters are typed with required fields, but there are no enums and `datetime` is any string PHP's strtotime accepts (8). Request examples, an error table and per-endpoint error codes (12). The path is versioned as v1, with no changelog found (3). Total 56.\n- 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.\n\n### Reliability: Acuity Scheduling API +43\n\n- Acuity Scheduling API (58): Graded as a hosted API. Statuspage site at status.acuityscheduling.com with incident history, though one component stands for the whole product (20). In the 90 days to 8 October 2026 the feed shows a critical disruption of 2 hours 5 minutes on 19 July and one of 18 minutes on 12 August, both marked as possibly affecting all users and services, plus a four-day iOS app fault and three minor integration incidents. Read as one major outage (10). 10 requests a second and 20 concurrent connections per IP (15). The 429 body is documented, with no `Retry-After`, backoff advice or idempotency key for booking writes (3). No SLA found, and the Developer Terms disclaim uninterrupted service (0). The v1 API is generally available (10). Total 58.\n- 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.\n\n### Agent ergonomics: Acuity Scheduling API +31\n\n- Acuity Scheduling API (44): `max` caps list size and `excludeForms` trims intake forms from appointments. No field selection (10). Filters by date, calendar, type and client, but no cursor or offset is documented, so long lists need date windows (10). Errors carry a status, a named code and a message, and a 404 suggests the nearest path (16). No idempotency key or safe-retry guidance for `POST /appointments` (0). Booking needs five fields and picks a calendar when none is given. SDKs exist for Node.js and PHP, both last released in 2019 (8). Total 44.\n- 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.\n\n### Maintenance \u0026 community: YouCanBookMe API +13\n\n- Acuity Scheduling API (15): No changelog or release notes found. The docs' own page dates show the OAuth guide edited on 1 October 2026 and the webhooks guide on 25 June 2026, which we count as the latest dated change (10). No three dated entries in 90 days (0). A developer email address and a support form, with no public issue tracker for the API (5). The Node.js and PHP SDKs were last tagged in July 2019 (0). No current package to assess (0). Total 15.\n- 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.\n\n### Transparency \u0026 trust: YouCanBookMe API +6\n\n- Acuity Scheduling API (55): Closed service under Squarespace's Developer Terms of 16 December 2025, with MIT SDKs (15). The privacy policy of 15 July 2026 names acuityscheduling.com and states no retention periods. The DPA of the same date promises deletion within 90 days of cancellation on written request (15). No deprecation policy, and the Developer Terms allow changes to developer tools without notice (0). Sub-processors are disclosed only on request by email, and data may move to any country where Squarespace or its sub-processors operate, the US in particular (4). Total 34.\n- 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.\n\n## Score by category\n\n| Category | Weight | Acuity Scheduling API | YouCanBookMe API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 58 | 15 | Acuity Scheduling API +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 56 | 10 | Acuity Scheduling API +46 |\n| Agent ergonomics | 13% (16.2 this run) | 44 | 13 | Acuity Scheduling API +31 |\n| Security \u0026 auth | 14% (17.5 this run) | 27 | 24 | Acuity Scheduling API +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 15 | 28 | YouCanBookMe API +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 55 | 61 | YouCanBookMe API +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **42.5 · E** | **22.5 · F** | |\n\n## Facts side by side\n\n| Fact | Acuity Scheduling API | YouCanBookMe API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Squarespace | AI Software (Capacity) UK Ltd, trading as YouCanBookMe |\n| Hosted endpoint | `https://acuityscheduling.com/api/v1` | `https://api.youcanbook.me/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Squarespace's Developer Terms. The Node.js and PHP SDKs are MIT | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | none | 2026-09-01 |\n| Terms last updated | 2025-12-16 | 2026-03-18 |\n| Privacy policy last updated | no date given | 2026-03-16 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 9.2k npm/wk | none |\n| Agent reviews | 2.5/5 (4) | none |\n\n## How the scores have moved\n\n### Acuity Scheduling API\n\n- no change on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n\n### YouCanBookMe API\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Acuity Scheduling API\n\n1. Call `/availability/dates` then `/availability/times` with `appointmentTypeID` before `POST /appointments`, which validates the slot as a client would\n2. Avoid `admin=true` unless the owner asks for it, because it skips availability and form validation\n3. Pass `noEmail=true` when a booking or cancellation must not send the client an email or SMS\n4. Check `GET /appointments` filtered by `email` and date before retrying a booking, since no idempotency key is documented\n5. Stay under 10 requests a second and 20 concurrent connections per IP, and back off on 429, which carries no documented `Retry-After`\n\n### YouCanBookMe API\n\n1. 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\n2. Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us\n3. Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented\n4. 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\n5. Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling\n\n## Questions\n\n### Which is better for AI agents, Acuity Scheduling API or YouCanBookMe API?\n\nAcuity Scheduling API scores 42.5 (E) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in 4 of 7 scored categories. YouCanBookMe API leads on maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Acuity Scheduling API and YouCanBookMe API need an API key?\n\nAcuity Scheduling API takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.\n\n### Can an agent call Acuity Scheduling API and YouCanBookMe API without installing anything?\n\nYes. Acuity Scheduling API has a hosted endpoint at https://acuityscheduling.com/api/v1 and YouCanBookMe API at https://api.youcanbook.me/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"acuity-scheduling\", \"b\": \"youcanbookme\"}`. From a terminal: `anchor compare acuity-scheduling youcanbookme`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/acuity-scheduling.json and https://www.anchorterminal.com/api/v1/tools/youcanbookme.json\n\n## Other comparisons with Acuity Scheduling API or YouCanBookMe API\n\n- [Acuity Scheduling API vs Agenda Hero](https://www.anchorterminal.com/compare/acuity-scheduling-vs-agenda-hero.md)\n- [Acuity Scheduling API vs Apiroc Unified Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-apiroc.md)\n- [Acuity Scheduling API vs Aurinko Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-aurinko-calendar.md)\n- [Acuity Scheduling API vs Cal.com API v2 + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cal-com.md)\n- [Acuity Scheduling API vs Calendly API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-calendly.md)\n- [Acuity Scheduling API vs Cozi Family Organizer](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cozi.md)\n- [Acuity Scheduling API vs Cronofy API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cronofy.md)\n- [Acuity Scheduling API vs Google Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-google-calendar-api.md)\n- [Acuity Scheduling API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-microsoft-graph-calendar.md)\n- [Acuity Scheduling API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.md)\n- [Acuity Scheduling API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.md)\n- [Acuity Scheduling API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler.md)\n- [Aurinko Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.md)\n- [Cal.com API v2 + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.md)\n- [Calendly API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.md)\n- [Cronofy API vs YouCanBookMe API](https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.md)\n- [Nylas Calendar and Scheduler API vs YouCanBookMe API](https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.md)\n- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)\n- [YouCanBookMe API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.md)\n- [Apiroc Unified Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.md)\n- [Google Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.md)\n- [Microsoft Graph Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Acuity Scheduling API vs YouCanBookMe API", "url": "" } ], "description": "Acuity Scheduling scores 42.5 (E) to YouCanBookMe's 22.5 (F) for calendar booking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Acuity Scheduling API E 42.5", "YouCanBookMe API F 22.5", "scores" ], "h1": "Acuity Scheduling API vs YouCanBookMe API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/acuity-scheduling-vs-youcanbookme", "published": "2026-10-01", "section": "tools", "title": "Acuity Scheduling vs YouCanBookMe for AI agents (2026)", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme" }, "tokens": { "markdown": 4400, "slim": 2380 }, "version": 1 }