AgentDrives
Free check
Closeclose.com

Can an AI agent use Close (close.com)?

As of 11 Oct 2026, an AI agent can't use Close on its own: Invisible reCAPTCHA refuses the sign-up.

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.

What the levels mean
Visit Close Follow changes

Driven 11 Oct 2026Same level in 3 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 agentsNot checked: its robots.txt asks crawlers to stay off the sign-up page.
  • 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 Close (close.com).

On its own

  • Read Close's help docs, API reference, and list of AI-assistant tools
  • Register a developer app identity without logging in

What it can't, and why

  • Create a Close accountAn invisible bot check on the sign-up page rejected the attempt with no visible test to pass
  • Get a working key or loginKeys are only made inside the app, which needs the account the agent couldn't create
  • Use any CRM feature (leads, calls, email, texting, tasks)None of this is reachable without an account
1 more
  • Start or cancel a paid planStarting a plan happens inside the app, behind the same sign-up wall
Blocked

Can an AI agent sign up for Close on its own?

No. Sign-up: blocked. No sign-up API. Browser form at app.close.com/signup/ refused after the password step: "We couldn't verify this signup.

Official server · no call worked

Does Close (close.com) have an MCP server, and can an agent connect to it?

Yes. Close has an official MCP server. The server lists 122 tools and signs an agent in with OAuth.

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). Through the MCP server, 0 of our agent's 1 attempt worked.

What the drive found

APIOpenAPIMCP · official–CLI–SDKllms.txtWebhooks–Sandbox

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

For the team behind Close.

Where agents stop in Close (close.com) today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Let verified agents pass the sign-up checkStep-by-step guide
  2. Offer a headless sign-up that returns a keyStep-by-step guide
  3. Allow /signup in app.close.com robots.txt
1 more fix
  1. Add a billing API or MCP upgrade tool 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 Close (close.com), 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. 1 Oct 2026L1Needs a person
  2. 6 Oct 2026L1Needs a person
  3. 11 Oct 2026L1Needs a person

For agents and builders.

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

How an agent connects · 4 tips

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

  • Once in, use the MCP server at https://mcp.close.com/mcp (OAuth with DCR, or an API key plus a Close-Scope header)
  • The REST API uses Basic auth with the API key as username and an empty password
  • Use app.close.com/signup/ with the slash: /signup is disallowed by robots.txt
  • Docs pages have .md versions; developer.close.com/llms.txt indexes them
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessllms.txt on close.com and developer.close.com, OpenAPI 3.1.0 (159 paths), .md docs pages
  2. Sign upBlockedNo sign-up API. Browser form at app.close.com/signup/ refused after the password step: "We couldn't verify this signup.
  3. VerifyNot reachedNot reached: sign-up refused
  4. KeyNot reachedAPI keys only in the web app (Settings > Developer > API Keys). OAuth DCR answered 201 headless, but authorizing needs a signed-in Close user; no device flow.
  5. First callNot reachedGET /api/v1/me/ without credentials: 401 {"error": "Unauthorized"}
  6. First actionNot reachedNot reached: no account
  7. PayNot reachedNo 402, x402, MPP, UCP or Stripe Projects listing; we paid nothing. Pricing: 14-day trial, no credit card required; plans $9-$139 per user/month. No billing API; MCP has read-only billing tools. Upgrade is inside the app behind the sign-up, not reached.
  8. CancelNot reachednot tested: no plan or trial was started because sign-up was refused before reaching the app; Close offers paid plans, so this is untested. No billing API or MCP billing write tool in the docs; help.close.com/docs/cancel-your-subscription 404.
  9. DeleteNot reachedNo account was created; the OpenAPI has no account delete route
The attempt log · 14 attempts
CapabilityRouteResultEvidence
docs: Find docs, llms.txt, OpenAPIapidone ✓close.com/llms.txt 200; developer.close.com/llms.txt 200 (index, MCP, OpenAPI links); developer.close.com/openapi.json openapi 3.1.0, 159 paths; .md page URLs return text/markdown
mcp: server/discover on https://mcp.close.com/mcpmcpblocked ✓POST server/discover -> 401 WWW-Authenticate Bearer resource_metadata=https://mcp.close.com/.well-known/oauth-protected-resource/mcp; PRM: AS https://api.close.com, scopes mcp.read, mcp.write_safe, mcp.write_destructive, offline_access
cards and preferences: server card, ai-catalog, agent-card, aipref, auth.mdapidone ✓<mcp>/server-card 404; /.well-known/ai-catalog.json 404; /.well-known/agent-card.json 404; /.well-known/agent.json 404; /.well-known/mcp/server-card.json 200 application/json (Close MCP, streamable-http, oauth2); close.com/robots.txt: Content-Signal: ai-train=no, search=yes (Cloudflare Content Signals form); close.com/auth.md 200 text/markdown (prose guide, no WorkOS agent_auth block); /.well-known/oauth-protected-resource on close.com 200
pay public probes: 402s, registries, checkout, trialapidone ✓pay_probe.json: no 402 challenges on close.com/api.close.com; x402./mpp./agents. no such host; no mpp/stripe projects/bazaar listings; /.well-known/ucp 404; pricing: free plan, Try for free ... No credit card required; pay_tx.json: refused, no 402 on own domain
sign up: Find a headless sign-up routenoneblocked ✓developer.close.com/llms.txt, auth.md and OpenAPI (159 paths) list no sign-up or organization-create route; auth.md: create keys in Close under Settings → API Keys; no auth.md agent_auth block in AS metadata
sign up: Sign up in the browser at app.close.com/signup/ with the agent's inbox, AgentDrives Testbrowserblocked ✓Email step accepted (Email saved: create your password); after password + Continue the page says: We could not verify this signup. Try a different browser or email support@close.com for assistance. Page carries invisible reCAPTCHA (This page is protected by reCAPTCHA); no visible challenge shown. Screenshot browser/shots/004.png
verify email: Read verification mailnoneblockedNot reached: sign-up rejected before any account was created
API credentials: Get an API key or OAuth token headlessapiblocked ✓API keys only in the web app (Settings → Developer → API Keys, developer.close.com/api/overview/[redacted].md). OAuth: DCR at https://api.close.com/oauth2/register/ answered 201 headless with client_id (public client, scopes mcp.read mcp.write_destructive mcp.write_safe offline_access); authorize needs a signed-in Close user at app.close.com/oauth2/authorize/ (robots.txt on app.close.com disallows it too); no device flow, no client_credentials grant
first API call: GET /api/v1/me/apiblocked ✓GET https://api.close.com/api/v1/me/ without credentials -> 401 {"error": "Unauthorized"} (application/json, not problem+json); RateLimit: limit=100; remaining=100; reset=1 plus ratelimit-limit/x-ratelimit-* legacy headers
first action: Create a leadapiblockedNot reached: no account and no credentials (sign-up rejected by invisible bot check)
pay step: Find how an agent could pay for a paid planapiblocked ✓close.com/pricing: Start your free 14-day trial, no credit card required; plans Solo $9, Essentials $35, Growth $99, Scale $139 per user/month billed annually. No 402 on close.com or api.close.com (pay_probe.json), no x402/MPP/UCP/Stripe Projects, no billing endpoints in the 159-path OpenAPI; MCP has read-only get_billing_summary / fetch_invoice / find_invoices, no upgrade tool. Checkout lives inside the app behind sign-up, not reached.
cancel: Cancel a plannoneskippednot tested: no plan or trial was started (sign-up rejected). No billing API or MCP billing write tool in the docs; help.close.com/docs/cancel-your-subscription 404
delete account: Delete the accountnoneblockedNo account was created (sign-up rejected), nothing to delete. OpenAPI has no account/organization delete route.
API credentials: Revoke the DCR client registered in this driveapiblockedAS metadata lists revocation_endpoint for tokens only; RFC 7591 registration response gave no registration_access_token / registration_client_uri, so the public client [redacted] cannot be deleted by us; it holds no grant and no token

Also in CRM.

All of CRM, by level