Copper vs folk for AI agents
As of 6 Oct 2026, both reach L1 · Needs a person. Our agent got further with folk: with folk it was stopped at verify (blocked), with Copper it was stopped at sign up (blocked).
- 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 evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't verify its account.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at verify: blocked. Next: let an agent verify its account on its own
Gets in only with a person: L1 · Needs a person. Our agent started sign-up itself at app.folk.app, but the emailed magic link runs Stytch Device Fingerprinting, and both links landed on a "Login Error" page instead of a session. Without that session, API keys stay locked in Settings, and MCP OAuth's authorize step sends an agent back to the same blocked magic link, so no key or token was ever issued. No CRM work was done through API, MCP or CLI. Docs are thorough: llms.txt, Markdown pages, OpenAPI, MCP guides. Paying and deleting the account both need a browser login our agent never reached, so neither was tested.
Gets furtherDriven 6 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.
CopperStopped at sign up: blocked
folkStopped at verify: blocked
| Checkpoint | Copper | folk |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | In a browser |
| Verify | In a browser | Blocked |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | In a browser | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Blocked | Not reached |
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
| Copper | folk | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 3 | 1 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 2 | 1 |
| Not tested (checkpoints) | 0 | 6 |
| Work done | 56% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | No | Yes (official) |
| CLI | No | No |
| SDK | No | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Copper | folk | |
|---|---|---|
| Bot check | None met | Stytch Device Fingerprinting (magic-link redirect) stopped it at verify, without a visible challenge |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | Google-only sign-up, API keys only in UI | Stytch fingerprint check blocks magic-link login |
| 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.
| Copper | folk | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 50 of 100, fair | 90 of 100, good |
| Standards | None recorded | MCP client registration (current) · OpenAPI 3.1.0 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Copper | folk | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not needed | Not reached |
| Delete the account | Blocked | Not reached |
How each one takes payment
- Copper: Reaches the checkout: stopped at the card form.
- folk: Payment not reached.
Copper vs folk: the short answers.
Which can an AI agent use, Copper or folk?
Both reach L1 · Needs a person. Our agent got further with folk: with folk it was stopped at verify (blocked), with Copper it was stopped at sign up (blocked). Driven 2 Oct 2026 (Copper) and 6 Oct 2026 (folk).
Can an AI agent sign up for Copper and folk on its own?
Copper: no, blocked. folk: yes, in a browser, but a later step stopped it.
Do Copper and folk have an MCP server?
Copper: none found. folk: yes (official).
Can an AI agent delete its Copper or folk account?
Copper: blocked. folk: not reached.
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.