Attio vs Salesforce for AI agents

As of 16 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

SalesforceL1Needs a person

Find: Some docs for agents: llms.txt and an MCP server.
Access: Signs up sometimes.
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

Salesforce is a CRM and AI-agent platform, but an agent working on its own could not even sign up: the free developer-account page and the trial sign-in are blocked by the site's anti-bot defenses, and the paid trial form asks for a phone number the agent doesn't have. Because no account or org could be created, none of the CRM, sales, service or AI-agent features could be tried.

Driven 16 Oct 2026 · The drive and its evidence

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

Where each one stops.

AttioThrough every checkpoint

SalesforceStopped at sign up: blocked

Attio and Salesforce, checkpoint by checkpoint
Checkpoint	Attio	Salesforce
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	Salesforce
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	No
MCP server	Yes (official)	Yes (official)
CLI	Yes	Yes
SDK	Yes	–
llms.txt	Yes	Yes

Bot checks, and where a person was needed.

Walls our agent met
	Attio	Salesforce
Bot check	None met	Akamai (developer.salesforce.com edge) 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	Akamai refuses sign-up pages; trial needs phone
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 Salesforce: level and part scores, 0 to 100
	Attio	Salesforce
Level	L4 · Runs on its own	L1 · Needs a person
Agent-ready setup	100 of 100, good	75 of 100, fair
Standards	None recorded	MCP client registration (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	Salesforce
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.
Salesforce: Payment not reached.

Attio vs Salesforce: the short answers.

Which can an AI agent use, Attio or Salesforce?

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 Salesforce it was stopped at sign up (blocked). Driven 2 Oct 2026 (Attio) and 16 Oct 2026 (Salesforce).

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

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

Do Attio and Salesforce have an MCP server?

Attio: yes (official). Salesforce: yes (official).

Can an AI agent delete its Attio or Salesforce account?

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