Salesforce 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: 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- 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.
SalesforceStopped at sign up: blocked
TwentyGot in; payment not reached
| Checkpoint | Salesforce | Twenty |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | 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
| Salesforce | Twenty | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 0 | 5 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 1 |
| Work done | Not measured | 80% of the core |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | – | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Salesforce | Twenty | |
|---|---|---|
| Bot check | Akamai (developer.salesforce.com edge) stopped it at sign up, without a visible challenge | reCAPTCHA (invisible) let it through at sign up |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Akamai refuses sign-up pages; trial needs phone | Got in; payment not reached |
| 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.
| Salesforce | Twenty | |
|---|---|---|
| Level | L1 · Needs a person | L4 · Runs on its own |
| Agent-ready setup | 75 of 100, fair | 100 of 100, good |
| Standards | MCP client registration (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.
| Salesforce | Twenty | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | In a browser |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Salesforce: Payment not reached.
- Twenty: Payment not reached.
Salesforce vs Twenty: the short answers.
Which can an AI agent use, Salesforce or Twenty?
Twenty gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Salesforce our agent was stopped at sign up (blocked); with Twenty it got in (payment not reached). Driven 16 Oct 2026 (Salesforce) and 2 Oct 2026 (Twenty).
Can an AI agent sign up for Salesforce and Twenty on its own?
Salesforce: no, blocked. Twenty: yes, in a browser.
Do Salesforce and Twenty have an MCP server?
Salesforce: yes (official). Twenty: yes (official).
Can an AI agent delete its Salesforce or Twenty account?
Salesforce: 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.