Close vs Copper for AI agents
As of 11 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (blocked).
- 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.
Stopped at sign up: blocked. Next: let an agent sign up on its own
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.
Driven 11 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt.
- Access: Can't sign up.
- Use: 56% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Nothing to cancel: Can't delete its account.
Stopped at sign up: blocked. Next: let an agent sign up on its own
Copper is a sales CRM built tightly around Gmail and Google accounts. Once our agent had an account and an API key, it ran the day-to-day sales work (contacts, deals, tasks, tags) entirely on its own. Getting in is the hard part: the sign-up page offers only Google, and API keys are made only on a settings page in the browser.
Driven 2 Oct 2026 · The drive and its evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
CloseStopped at sign up: blocked
CopperStopped at sign up: blocked
| Checkpoint | Close | Copper |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Blocked |
| Verify | Not reached | In a browser |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Close | Copper | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 0 | 3 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 2 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 56% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | No |
| CLI | No | No |
| SDK | No | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Close | Copper | |
|---|---|---|
| Bot check | reCAPTCHA (invisible) stopped it at sign up, without a visible challenge | None met |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Invisible reCAPTCHA refuses the sign-up | Google-only sign-up, API keys only in UI |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| Close | Copper | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 50 of 100, fair |
| Standards | MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | None recorded |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Close | Copper | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- Close: Payment not reached.
- Copper: Reaches the checkout: stopped at the card form.
Close vs Copper: the short answers.
Which can an AI agent use, Close or Copper?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (blocked). Driven 11 Oct 2026 (Close) and 2 Oct 2026 (Copper).
Can an AI agent sign up for Close and Copper on its own?
Close: no, blocked. Copper: no, blocked.
Do Close and Copper have an MCP server?
Close: yes (official). Copper: none found.
Can an AI agent delete its Close or Copper account?
Close: not reached. Copper: blocked.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.