Close vs Salesforce for AI agents
As of 16 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (blocked).
- 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- 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.
CloseStopped at sign up: blocked
SalesforceStopped at sign up: blocked
| Checkpoint | Close | Salesforce |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Blocked |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | 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
| Close | Salesforce | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 1 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | No | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Close | Salesforce | |
|---|---|---|
| Bot check | reCAPTCHA (invisible) stopped it at sign up, without a visible challenge | Akamai (developer.salesforce.com edge) stopped it at sign up, without a visible challenge |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Invisible reCAPTCHA refuses the sign-up | 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.
| Close | Salesforce | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 75 of 100, fair |
| Standards | MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | 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.
| Close | Salesforce | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Close: Payment not reached.
- Salesforce: Payment not reached.
Close vs Salesforce: the short answers.
Which can an AI agent use, Close or Salesforce?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (blocked). Driven 11 Oct 2026 (Close) and 16 Oct 2026 (Salesforce).
Can an AI agent sign up for Close and Salesforce on its own?
Close: no, blocked. Salesforce: no, blocked.
Do Close and Salesforce have an MCP server?
Close: yes (official). Salesforce: yes (official).
Can an AI agent delete its Close or Salesforce account?
Close: not reached. 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.