Attio vs Twenty for AI agents

As of 2 Oct 2026, both reach L4 · Runs on its own. Our agent got further with Attio: with Attio it went through every checkpoint, with Twenty it got in (payment not reached).

AttioL4Runs on its own

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
Access: Sign-up in a browser.
Use: 100% of the work.
Pay: Reaches the checkout: Stopped at the card form.
Leave: Leaves on its own: Cancels on its own, deletes its account.

Through every checkpoint. Next: pay without a person

Our agent gets in on its own: L4 · Runs on its own. Sign-up, email verification and token creation all needed a browser, with no bot check anywhere in the flow. Once the token existed, our agent created and read back a company record through Attio's documented REST API, work also covered by its official MCP server. Workflows, sequences and billing stayed browser-only. There was nothing recurring to cancel, and deleting the workspace removed its data and shut off the API token, though the underlying Attio login itself stayed.

Gets furtherDriven 2 Oct 2026 · The drive and its evidence

TwentyL4Runs on its own

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.

Driven 2 Oct 2026 · The drive and its evidence

The two summaries: written and checked by our agents from each product's drive. How we write.

Attio or Twenty: what the difference means.

Twenty's sign-up page carries invisible reCAPTCHA, and our signed agent passed without seeing a challenge; Attio's sign-up has no CAPTCHA at all. Neither drive stopped before L4 · Runs on its own. The gap is at paying: Attio's Stripe card form under Settings > Plans rendered for our agent's browser, unfilled. Twenty's 'Add credit card' button did nothing when clicked: no popup, no Stripe request, with an hCaptcha script on the page. Paying stops there for an agent working alone.

For an agent builder

Pick Attio for straightforward CRM record work over REST, with a trial that starts without a card. Pick Twenty for workflow-heavy work: custom objects, views and AI-agent steps through its MCP and REST/GraphQL. Our agent creates the credential itself in a browser on either. Attio's access token sits under Settings > Developers; Twenty's API key is shown once, captured only after a regeneration. Paying needs a person on either.

For the owners

Attio's docs could state a sign-up policy for agents the way Twenty's llms.txt does, which already states that agent-driven sign-up is allowed. Twenty's billing button should answer an automated browser the way Attio's Settings > Plans form does, where the card page at least renders unfilled. Then paying shows what it asks for instead of a dead click.

Written and checked by our agents from both drives, on 14 Oct 2026. How we write.

Where each one stops.

AttioThrough every checkpoint

TwentyGot in; payment not reached

Attio and Twenty, checkpoint by checkpoint
Checkpoint	Attio	Twenty
Docs	Headless	Headless
Sign up	In a browser	In a browser
Verify	In a browser	In a browser
Key	In a browser	In a browser
First call	Headless	Headless
First action	Headless	Headless
Pay	In a browser	Not reached
Cancel	In a browser	In a browser
Delete	In a browser	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

Checkpoints by how our agent passed them, and what each product offers an agent
	Attio	Twenty
Headless (checkpoints)	3	3
In a browser (checkpoints)	6	5
Needs a human (checkpoints)	0	0
Blocked (checkpoints)	0	0
Not tested (checkpoints)	0	1
Work done	100% of the core	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.

Walls our agent met
	Attio	Twenty
Bot check	None met	reCAPTCHA (invisible) let it through at sign up
Wall type	No bot-check wall	No bot-check wall
First wall	None	Got in; payment not reached
A person helped	No	No

Level and part scores.

Attio and Twenty: level and part scores, 0 to 100
	Attio	Twenty
Level	L4 · Runs on its own	L4 · Runs on its own
Agent-ready setup	100 of 100, good	100 of 100, good

Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.

Pay, cancel and delete.

Paying, cancelling and deleting the account
	Attio	Twenty
Pay	Reaches the checkout	Payment not reached
Free plan or trial	Trial, no card	Trial, no card
Cancel	In a browser	In a browser
Delete the account	In a browser	In a browser

How each one takes payment

Attio: Reaches the checkout: stopped at the card form.
Twenty: Payment not reached.

Attio vs Twenty: the short answers.

Which can an AI agent use, Attio or Twenty?

Both reach L4 · Runs on its own. Our agent got further with Attio: with Attio it went through every checkpoint, with Twenty it got in (payment not reached). Both driven 2 Oct 2026.

Can an AI agent sign up for Attio and Twenty on its own?

Attio: yes, in a browser. Twenty: yes, in a browser.

Do Attio and Twenty have an MCP server?

Attio: yes (official). Twenty: yes (official).

Can an AI agent delete its Attio or Twenty account?

Attio: yes, in a browser. Twenty: yes, in a browser.