Copper vs HubSpot for AI agents
As of 16 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Copper it was stopped at sign up (blocked), with HubSpot it was stopped at sign up (needs a human).
- 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; a docs page for each core task.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
HubSpot is a CRM and marketing platform with good developer docs for AI agents, but an agent cannot sign up on its own: the sign-up form shows a 'prove you're human' checkbox before it will even send a verification code. Because of that, nothing on the CRM, no payment, and no account deletion could be tried.
Driven 16 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
HubSpotStopped at sign up: needs a human
| Checkpoint | Copper | HubSpot |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Needs a human |
| Verify | In a browser | Not reached |
| 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 | HubSpot | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 3 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 2 | 0 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 56% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | No | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Copper | HubSpot | |
|---|---|---|
| Bot check | None met | Google reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge |
| Wall type | No bot-check wall | A challenge on the form |
| First wall | Google-only sign-up, API keys only in UI | Visible reCAPTCHA checkbox on email sign-up |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Copper | HubSpot | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 50 of 100, fair | 100 of 100, good |
| Standards | None recorded | OpenAPI 3.0.1 (2 versions behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Copper | HubSpot | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Trial, no card | Free plan |
| 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.
- HubSpot: Payment not reached.
Copper vs HubSpot: the short answers.
Which can an AI agent use, Copper or HubSpot?
Both reach L1 · Needs a person, and our agent got as far with each: with Copper it was stopped at sign up (blocked), with HubSpot it was stopped at sign up (needs a human). Driven 2 Oct 2026 (Copper) and 16 Oct 2026 (HubSpot).
Can an AI agent sign up for Copper and HubSpot on its own?
Copper: no, blocked. HubSpot: no, needs a human.
Do Copper and HubSpot have an MCP server?
Copper: none found. HubSpot: yes (official).
Can an AI agent delete its Copper or HubSpot account?
Copper: blocked. HubSpot: 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.