AgentDrives
Free check
Acuity Schedulingacuityscheduling.com

Can an AI agent use Acuity Scheduling?

As of 11 Oct 2026, an AI agent can't use Acuity Scheduling on its own: Invisible reCAPTCHA stalls the Squarespace sign-up form.

Level 1 · Needs a personAgents can't get in on their own.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

Got in on 1 of 3 drives: the bot check let it through in some and not in others.

What the levels mean
Visit Acuity Scheduling Follow changes

Driven 11 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

  • Agents on a serverTurned away when they send the sign-up form.
  • Signed agentsThe site opens. The check on the form still applies.
  • Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Acuity Scheduling.

On its own

  • Read all the developer documentation in a clean, agent-friendly format.

What it can't, and why

  • Create an accountThe sign-up form silently stalls behind an invisible bot check with no error message.
  • Call the booking APIThe website's own robots rules block the documented API address for all automated tools.
  • Get an API key on its ownKeys are only available inside the web dashboard after logging in.
Blocked

Can an AI agent sign up for Acuity Scheduling on its own?

No. Sign-up: blocked. Sign-up is a Squarespace account form (login.squarespace.com). After CONTINUE the button stayed disabled with no error and no request sent; an invisible reCAPTCHA Enterprise check sits on the form, no visible challenge. No API route to sign up.

No MCP server found

Does Acuity Scheduling have an MCP server, and can an agent connect to it?

No. The drive found no MCP server for Acuity Scheduling.

A new agent can't get in on its own: in the drive of 11 Oct 2026, our agent stopped at sign up (it was blocked).

What the drive found

APIOpenAPI–MCP–CLISDKllms.txtWebhooks–Sandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Acuity Scheduling.

Where agents stop in Acuity Scheduling today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Allow agents on the API in robots.txt
  2. Let signed agents through sign-upStep-by-step guide
  3. Show an error when sign-up is refused
2 more fixes
  1. Add an API to create and revoke keys Step-by-step guide
  2. Publish auth metadata for the docs MCP Step-by-step guide
  • Claim it free and reply next to the result.
  • A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
  • Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Get a DriveClaim it free
See the example report
Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

Driven · L1 · Needs a person badge

Behind the level.

Our agent couldn't get into Acuity Scheduling, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

  • llms.txt
  • OpenAPI
  • MCP server
  • CLI

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

  1. 2 Oct 2026L3Does the work
  2. 6 Oct 2026sign-up variesL1Needs a person
  3. 11 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 15 attempts.

How an agent connects · 3 tips

/api/tools/acuityscheduling.json/tools/acuityscheduling.mdMCP get_tool {"slug":"acuityscheduling"}

  • Read docs via developers.acuityscheduling.com/llms.txt and the .md pages
  • The documented API base acuityscheduling.com/api/v1 is disallowed by robots.txt: a robots-respecting agent cannot call it
  • Sign-up goes through a Squarespace account form with invisible reCAPTCHA Enterprise
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessPublic docs at developers.acuityscheduling.com with llms.txt, Markdown pages (.md and Accept: text/markdown) and an embedded OpenAPI 3.1.0.
  2. Sign upBlockedSign-up is a Squarespace account form (login.squarespace.com). After CONTINUE the button stayed disabled with no error and no request sent; an invisible reCAPTCHA Enterprise check sits on the form, no visible challenge. No API route to sign up.
  3. VerifyNot reachedNot reached: the sign-up was never submitted, no mail arrived.
  4. KeyNot reachedNot reached. Docs: the API key is shown only in the web app under Integrations; OAuth2 clients are registered on a web page. No API or CLI to create a key.
  5. First callNot reachedrobots.txt on acuityscheduling.com has 'Disallow: /api/*' for every user agent, which covers the documented API base https://acuityscheduling.com/api/v1.
  6. First actionNot reachedNot reached: no account, and the API is disallowed by robots.txt.
  7. PayNot reachedNo 402 challenges, no registry listing, no /.well-known/ucp, no billing API. Pricing page: '7-day trial, no credit card needed'; paid plans are picked in the web app after sign-up. We paid nothing: no 402 on the product's own domain asks for USDC. The checkout itself was not reached, so its processor is unknown.
  8. CancelNot reachednot tested: Acuity has paid plans but no plan or trial was started (sign-up blocked by the invisible reCAPTCHA); docs list no billing API, cancelling is in the web app (not reached).
  9. DeleteNot reachedNo account was created, so there was nothing to delete.
The attempt log · 15 attempts
CapabilityRouteResultEvidence
robots.txt: Read robots.txt on acuityscheduling.com and secure.acuityscheduling.comapidone ✓GET https://acuityscheduling.com/robots.txt 200: 'User-agent: *' group with 'Disallow: /api/*' (also /home.php, /appointments.php, /reports.php). Same file on secure.acuityscheduling.com. No Content-Usage or Content-signal lines.
llms.txt: Find llms.txtapidone ✓https://acuityscheduling.com/llms.txt 404; https://developers.acuityscheduling.com/llms.txt 200 text/plain, H1 'Acuity Scheduling Documentation', links to .md pages
Markdown docs: Accept: text/markdown and .md URL on a docs pageapidone ✓GET reference/quick-start with Accept: text/markdown -> content-type text/markdown, vary: Accept, Accept-Encoding; reference/quick-start.md 200 text/markdown
OpenAPI: Locate the OpenAPIapidone ✓reference/post-appointments.md embeds an OpenAPI block: "openapi": "3.1.0", servers url https://acuityscheduling.com/api/v1. developers.acuityscheduling.com/openapi.json 404.
Well-known cards: AI catalog, A2A card, PRM, AS metadata, UCPapidone ✓acuityscheduling.com: /.well-known/ai-catalog.json, agent-card.json, oauth-protected-resource, oauth-authorization-server, ucp all 404 text/html. developers host: ai-catalog.json 404, oauth-protected-resource 404, mcp/server-card.json 404.
MCP: server/discover on MCP endpointsmcppartial ✓POST https://developers.acuityscheduling.com/mcp (server/discover, MCP-Protocol-Version 2026-07-28) -> 401 application/json {"code":-32001,"message":"Authorization required"}, WWW-Authenticate: Bearer realm="mcp" (no resource_metadata). initialize also 401. /mcp/server-card 404. acuityscheduling.com/mcp 404.
Find docs: Find API docsapidone ✓developers.acuityscheduling.com quick-start: Basic Auth with numeric User ID + API Key found 'under Integrations' in the web app; OAuth2 docs; webhooks docs
Pay step public probes: Read pay_probe/pay_tx, check 402s and checkoutapidone ✓pay_probe.json: no 402 challenges, no registry listings, no /.well-known/ucp; pricing page: 'Start free trial 7-day trial, no credit card needed', Starter $16/month (annual). pay_tx.json status refused: 'no 402 on the product's own domain asks for USDC on a network we hold a wallet for'. Docs llms.txt has no billing API.
Sign up: Start the 7-day no-card trial (Squarespace account)browserblockedget-started redirects to login.squarespace.com OAuth 'Create your account'. Filled first/last name, the agent's inbox, password; CONTINUE pressed. Button went disabled and stayed disabled for >60 s with no error; no sign-up request was sent (page resource log shows no XHR/fetch to Squarespace's API after the click); invisible reCAPTCHA Enterprise anchor (size=invisible, key 6LeadacZ…) on the page; no visible challenge. No mail arrived.
Verify email: Read verification mailnoneblockedinbox read the agent's inbox --wait: 'No mail for the agent's inbox'
Get API key: Get User ID + API keynoneblockedQuick-start: key is shown in the web app 'under Integrations' (secure.acuityscheduling.com/app.php?action=settings&key=api); no API/CLI to create keys; OAuth2 needs a client registered at acuityscheduling.com/oauth2/register (web).
First API call: GET /api/v1/meapiblocked
Create something: Create an appointment type / appointmentnoneblockedNo account (sign-up stalled); API disallowed by robots.txt.
Cancel plan: Cancel trial/plannonen/aNo trial was started. Pricing page: 7-day trial, no credit card needed; docs list no billing API.
Delete account: Delete the accountnonen/aNo account was created.

Also in Scheduling.

All of Scheduling, by level