Attio vs Close for AI agents

As of 11 Oct 2026, Attio gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.

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

CloseL1Needs a person

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

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

Where each one stops.

AttioThrough every checkpoint

CloseStopped at sign up: blocked

Attio and Close, checkpoint by checkpoint
Checkpoint	Attio	Close
Docs	Headless	Headless
Sign up	In a browser	Blocked
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	In a browser	Not reached
Delete	In a browser	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

Checkpoints by how our agent passed them, and what each product offers an agent
	Attio	Close
Headless (checkpoints)	3	1
In a browser (checkpoints)	6	0
Needs a human (checkpoints)	0	0
Blocked (checkpoints)	0	1
Not tested (checkpoints)	0	7
Work done	100% of the core	Not measured
API	Yes	Yes
OpenAPI	Yes	Yes
MCP server	Yes (official)	Yes (official)
CLI	Yes	No
SDK	Yes	No
llms.txt	Yes	Yes

Bot checks, and where a person was needed.

Walls our agent met
	Attio	Close
Bot check	None met	reCAPTCHA (invisible) stopped it at sign up, without a visible challenge
Wall type	No bot-check wall	A check of our network and browser
First wall	None	Invisible reCAPTCHA refuses the 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. Where we drive from.

Level and part scores.

Attio and Close: level and part scores, 0 to 100
	Attio	Close
Level	L4 · Runs on its own	L1 · Needs a person
Agent-ready setup	100 of 100, good	90 of 100, good
Standards	None recorded	MCP client registration (behind) · 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.

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

How each one takes payment

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

Attio vs Close: the short answers.

Which can an AI agent use, Attio or Close?

Attio gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Attio our agent went through every checkpoint; with Close it was stopped at sign up (blocked). Driven 2 Oct 2026 (Attio) and 11 Oct 2026 (Close).

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

Attio: yes, in a browser. Close: no, blocked.

Do Attio and Close have an MCP server?

Attio: yes (official). Close: yes (official).

Can an AI agent delete its Attio or Close account?

Attio: yes, in a browser. Close: not reached.