Close 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 Close it was stopped at sign up (blocked), with HubSpot it was stopped at sign up (needs a human).
- 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: 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.
CloseStopped at sign up: blocked
HubSpotStopped at sign up: needs a human
| Checkpoint | Close | HubSpot |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Needs a human |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | 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
| Close | HubSpot | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Close | HubSpot | |
|---|---|---|
| Bot check | reCAPTCHA (invisible) stopped it at sign up, without a visible challenge | Google reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A challenge on the form |
| First wall | Invisible reCAPTCHA refuses the sign-up | Visible reCAPTCHA checkbox on email sign-up |
| 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. 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.
| Close | HubSpot | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | 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.
| Close | HubSpot | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Close: Payment not reached.
- HubSpot: Payment not reached.
Close vs HubSpot: the short answers.
Which can an AI agent use, Close or HubSpot?
Both reach L1 · Needs a person, and our agent got as far with each: with Close it was stopped at sign up (blocked), with HubSpot it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Close) and 16 Oct 2026 (HubSpot).
Can an AI agent sign up for Close and HubSpot on its own?
Close: no, blocked. HubSpot: no, needs a human.
Do Close and HubSpot have an MCP server?
Close: yes (official). HubSpot: yes (official).
Can an AI agent delete its Close or HubSpot account?
Close: not reached. 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.