Pipedrive vs Salesforce for AI agents
As of 16 Oct 2026, Pipedrive gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 71% of the work.
- Pay: Payment not reached.
- Leave: Nothing to cancel: Can't delete its account.
Got in; payment not reached. Next: do 80% of the core work (now 71%)
Our agent gets in on its own: L3 · Does the work, through the free developer sandbox form in a browser, no bot check met along the way. Deletion stopped it first: it deleted every record it created through the API, but found no account or company delete, only "Leave company," with inactive sandboxes purged later. Through the API and the official MCP server it created, moved, converted, searched, filtered and deleted CRM data end to end. Paying needs a human too: the pricing page returned a Cloudflare block, and the regular trial sign-up gave a generic error, so a person has to start the trial and checkout.
Gets furtherDriven 2 Oct 2026 · The drive and its evidence- 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 evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
PipedriveGot in; payment not reached
SalesforceStopped at sign up: blocked
| Checkpoint | Pipedrive | Salesforce |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Blocked |
| Verify | Not needed | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Blocked | 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
| Pipedrive | Salesforce | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 2 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 1 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | 71% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | Yes | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Pipedrive | 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 | Got in; payment not reached | 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.
| Pipedrive | Salesforce | |
|---|---|---|
| Level | L3 · Does the work | 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.
| Pipedrive | Salesforce | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not needed | Not reached |
| Delete the account | Blocked | Not reached |
How each one takes payment
- Pipedrive: Payment not reached.
- Salesforce: Payment not reached.
Pipedrive vs Salesforce: the short answers.
Which can an AI agent use, Pipedrive or Salesforce?
Pipedrive gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Pipedrive our agent got in (payment not reached); with Salesforce it was stopped at sign up (blocked). Driven 2 Oct 2026 (Pipedrive) and 16 Oct 2026 (Salesforce).
Can an AI agent sign up for Pipedrive and Salesforce on its own?
Pipedrive: yes, in a browser. Salesforce: no, blocked.
Do Pipedrive and Salesforce have an MCP server?
Pipedrive: yes (official). Salesforce: yes (official).
Can an AI agent delete its Pipedrive or Salesforce account?
Pipedrive: blocked. Salesforce: not reached.
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.