Acuity Scheduling — can an agent use it?
Acuity has a clean, documented REST API that covers its core action (booking appointments) and publishes an llms.txt on its developer hub. No official MCP server, but the API is simple enough that community wrappers work. The Premium plan gates API access at $49/mo, and there is no sandbox — agents must test against live calendars.
FIND & RETRIEVE · 7.0
ACT & TRANSACT · 4.2
TRUST & DURABILITY · 6.8
FIND & RETRIEVE7.0/10Can an agent get correct information?
Machine-readable surface6.5/10
The main site renders clean HTML without JS dependency (790 words visible to non-JS crawlers), has a valid sitemap with fresh lastmod dates, and multi-language sitemaps. The developer hub at developers.acuityscheduling.com publishes an llms.txt with a markdown index of all pages and supports appending .md to any documentation URL for markdown versions. However, the main site has no JSON-LD structured data, no schema.org markup, and no RSS feed. source
Information retrieval quality7.5/10
Pricing is published in detail on a clean, JS-free page: Starter $20/mo, Standard $34/mo, Premium $49/mo (annual discounts available), with a full feature comparison table showing what each tier includes. The 250,000+ customer figure is stated. Plan differences are clear (1 vs 6 vs 36 calendars, text reminders, HIPAA, API access). This is the kind of page an agent can scrape and answer questions from. source
Documentation for machines7/10
The developer hub has guides (getting started, embeds, CSS, webhooks), an API reference covering appointments (CRUD), payments, and metadata endpoints, plus OAuth2 documentation. The llms.txt indexes all pages and notes markdown availability. Clear code examples with curl. However, the API surface documented is narrow (appointments, availability, payments, meta) compared to the full product feature set, and rate limits are not documented anywhere visible. source
ACT & TRANSACT4.2/10Can an agent do the job?
Action coverage6.5/10
The API covers the core booking action: list appointments, create appointments, update appointments, check availability (dates, times, classes), and retrieve payment transactions. An agent can book on behalf of a client, check open slots, and manage existing bookings. Gaps: no documented endpoints for managing appointment types, staff/calendars, packages, memberships, gift certificates, or the waitlist — all of which are UI-accessible features. source
Agent protocol support2.5/10
No official MCP server from Acuity or Squarespace. Multiple community-maintained MCP wrappers exist (Zapier MCP with 24 tools, viaSocket, mcpbundles.com, and a GitHub repo). These cover appointment CRUD and client management but are third-party maintained. The API is simple enough that wrapping it is straightforward, but the absence of an official protocol surface means agents depend on community maintenance. source
Access & auth friction6/10
Two auth methods: HTTP Basic Auth with a numeric User ID + API key (found in Integrations settings — self-serve, no approval gate) and OAuth2 for multi-account integrations. Credentials are available immediately on signup. The friction is that API access requires the Premium plan ($49/mo), but once you are on that plan, keys are instant. No scoped/restricted keys — the API key has full access to the account. source
Agent payment capability1.5/10
Acuity processes payments through Stripe, Square, PayPal, and Venmo integrations, but the payment flow requires human interaction on the booking page or through these third-party processors. The API can retrieve payment transactions for appointments but cannot initiate payments programmatically. No support for any agent payment protocol (ACP, AP2, MPP, x402). An agent can book an appointment but cannot pay for it on behalf of a client. source
Cost & rate fairness4.5/10
API access is locked to the Premium tier at $49/mo ($588/yr) — the two cheaper tiers ($20 and $34/mo) do not include API or custom CSS access. Rate limits exist but are not documented anywhere in the public developer docs, which is a red flag for an agent that needs to plan around throttling. No free tier for developers to test against. No sandbox environment — the docs explicitly state you must make real API calls. The pricing page lists 'Custom API and CSS' as a Premium-only feature. source
TRUST & DURABILITY6.8/10Will it still work next quarter?
Permission & ToS stance6/10
robots.txt does not block AI crawlers specifically — the Disallow rules are functional (blocking /schedule.php action params, admin pages, and /api/*). The developer terms reference exists in the footer. The robots.txt blocking /api/* is notable — it prevents crawlers from discovering or indexing API responses, though this is a reasonable security measure. No evidence of hostile enforcement against automated access. Squarespace (parent company) has standard platform ToS but no specific anti-bot provisions visible in Acuity's developer-facing docs. source
Reliability & continuity7.5/10
Dedicated Statuspage at status.acuityscheduling.com (powered by Atlassian Statuspage) shows 99.84% uptime over 90 days with no incidents reported in the last 10 days. Email and SMS incident notifications available. The API has been stable — versioned at v1 for years without breaking changes. Squarespace ownership (since 2019) provides financial stability. The narrow API surface (appointments/availability/payments/meta) means fewer endpoints to break. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- acuityscheduling.com — home (accessed 2026-09-08)
- acuityscheduling.com/pricing — pricing with plan comparison (accessed 2026-09-08)
- acuityscheduling.com/robots.txt — robots (accessed 2026-09-08)
- acuityscheduling.com/sitemap.xml — sitemap (accessed 2026-09-08)
- developers.acuityscheduling.com — developer hub with llms.txt (accessed 2026-09-08)
- developers.acuityscheduling.com/llms.txt — llms.txt index (accessed 2026-09-08)
- developers.acuityscheduling.com/reference/quick-sta… — API quick start and auth (accessed 2026-09-08)
- status.acuityscheduling.com — status page (99.84% uptime) (accessed 2026-09-08)
- zapier.com/mcp/acuity-scheduling — community MCP (24 tools) (accessed 2026-09-08)