# Close: L1 · Needs a person

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

Source: https://agentdrives.com/tools/close?via=md · driven 11 Oct 2026 by AgentDrives's agent · Same level in 3 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

A person is needed before any agent work starts: L1 · Needs a person. Our agent's browser signup at app.close.com stopped after the password step, refused by an invisible reCAPTCHA with no challenge to solve: "We couldn't verify this signup." Every later checkpoint, from key to first call, went untested because no account existed. The product's agent surface otherwise holds up well: llms.txt, an OpenAPI spec, Markdown docs, and an official MCP server whose OAuth client registration worked headlessly, though authorizing still needs a signed-in person. The trial needs no card, and paying or leaving were never reached.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- Find: Docs for agents (llms.txt, an OpenAPI and an MCP server)
- Access: Can't sign up
- Use: Work not reached
- Pay: Payment not reached
- Leave: Leaving not reached
- Next: let an agent sign up on its own
- With an account set up by a person: not measured yet.

## Level history

- 1 Oct 2026: L1 · Needs a person
- 6 Oct 2026: L1 · Needs a person
- 11 Oct 2026: L1 · Needs a person

## Part scores

- Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI not found
- Not measured in this drive: Holds up, Docs match

## Who gets in

- Agents on a server: Turned away when they send the sign-up form.
- Signed agents: Not checked: its robots.txt asks crawlers to stay off the sign-up page.
- Agents in a person's browser: Not measured yet.

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

## Checkpoints

- **Docs**: Headless: llms.txt on close.com and developer.close.com, OpenAPI 3.1.0 (159 paths), .md docs pages
- **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.
- **Verify**: Not reached: Not reached: sign-up refused
- **Key**: Not reached: API 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.
- **First call**: Not reached: GET /api/v1/me/ without credentials: 401 {"error": "Unauthorized"}
- **First action**: Not reached: Not reached: no account
- **Pay**: Not reached: No 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.
- **Cancel**: Not reached: not 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.
- **Delete**: Not reached: No account was created; the OpenAPI has no account delete route

## 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.

## How does an AI agent get a Close (close.com) API key?

Not reached: in the drive of 11 Oct 2026, sign-up stopped our agent first (it was blocked). API 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.

## Paying the agent way

Payment not reached.

No card needed to start.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
Ways to pay checked 11 Oct 2026.

## What an agent can do

- Read Close's docs, OpenAPI and MCP tool list as Markdown
- Register an OAuth client by Dynamic Client Registration without an account

## What it cannot do

- Sign up for a Close account: The sign-up form's invisible reCAPTCHA refused our agent's browser with no challenge to solve
- Get an API key or OAuth token: Keys are made only in the web app and OAuth consent needs a signed-in user
- Use any CRM capability (leads, opportunities, calls, email, SMS, tasks): No account

## Tips for the owner

1. Let verified agents pass the sign-up check
2. Offer a headless sign-up that returns a key
3. Allow /signup in app.close.com robots.txt
4. Add a billing API or MCP upgrade tool

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in CRM

- [Attio](https://agentdrives.com/tools/attio.md?via=md): L4 · Runs on its own · [Close vs Attio](https://agentdrives.com/compare/attio-vs-close?via=md)
- [Twenty](https://agentdrives.com/tools/twenty.md?via=md): L4 · Runs on its own · [Close vs Twenty](https://agentdrives.com/compare/close-vs-twenty?via=md)
- [Pipedrive](https://agentdrives.com/tools/pipedrive.md?via=md): L3 · Does the work · [Close vs Pipedrive](https://agentdrives.com/compare/close-vs-pipedrive?via=md)
- [Copper](https://agentdrives.com/tools/copper.md?via=md): L1 · Needs a person · [Close vs Copper](https://agentdrives.com/compare/close-vs-copper?via=md)
- [folk](https://agentdrives.com/tools/folk.md?via=md): L1 · Needs a person · [Close vs folk](https://agentdrives.com/compare/close-vs-folk?via=md)
- [HubSpot](https://agentdrives.com/tools/hubspot.md?via=md): L1 · Needs a person · [Close vs HubSpot](https://agentdrives.com/compare/close-vs-hubspot?via=md)
- [Salesforce](https://agentdrives.com/tools/salesforce.md?via=md): L1 · Needs a person · [Close vs Salesforce](https://agentdrives.com/compare/close-vs-salesforce?via=md)

## Tips for agent builders

- 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