HubSpot vs Twenty for AI agents
As of 16 Oct 2026, Twenty gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- 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 evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 80% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Cancels on its own, deletes its account.
Got in; payment not reached. Next: pay without a person
Runs on its own: L4 · Runs on its own. Signup, onboarding and the first key need a browser, and invisible reCAPTCHA let our agent through with no challenge shown. Paying is where it stopped: a trial starts without a card, but clicking add credit card at checkout did nothing in our agent's browser, so a person has to add the card. Short of that, Twenty worked headless: REST and an official MCP server let it create a company and read it back, with tools covering records, custom objects, views and workflows. Cancelling and deleting the workspace both worked on their own, with no card ever added.
Gets furtherDriven 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.
HubSpotStopped at sign up: needs a human
TwentyGot in; payment not reached
| Checkpoint | HubSpot | Twenty |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| 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 | Not reached |
| Cancel | Not reached | In a browser |
| Delete | Not reached | In a browser |
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
| HubSpot | Twenty | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 0 | 5 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 1 |
| Work done | Not measured | 80% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| HubSpot | Twenty | |
|---|---|---|
| Bot check | Google reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge | reCAPTCHA (invisible) let it through at sign up |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | Visible reCAPTCHA checkbox on email sign-up | Got in; payment not reached |
| 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.
| HubSpot | Twenty | |
|---|---|---|
| Level | L1 · Needs a person | L4 · Runs on its own |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | OpenAPI 3.0.1 (2 versions 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.
| HubSpot | Twenty | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not reached | In a browser |
| Delete the account | Not reached | In a browser |
How each one takes payment
- HubSpot: Payment not reached.
- Twenty: Payment not reached.
HubSpot vs Twenty: the short answers.
Which can an AI agent use, HubSpot or Twenty?
Twenty gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With HubSpot our agent was stopped at sign up (needs a human); with Twenty it got in (payment not reached). Driven 16 Oct 2026 (HubSpot) and 2 Oct 2026 (Twenty).
Can an AI agent sign up for HubSpot and Twenty on its own?
HubSpot: no, needs a human. Twenty: yes, in a browser.
Do HubSpot and Twenty have an MCP server?
HubSpot: yes (official). Twenty: yes (official).
Can an AI agent delete its HubSpot or Twenty account?
HubSpot: not reached. Twenty: yes, in a browser.
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.