Compare

Close vs Salesforce

Close scores higher on the AgentReady, 74/100 against 43/100. They differ on 16 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Close. Close is a sales CRM built for teams that sell, combining calling, email, SMS, pipeline management, reporting, and an AI sales agent named Chloe into a single platform.

Salesforce. Salesforce is the #1 Agentic CRM, providing a platform where agents, teams, and data work together so every customer interaction reflects businesses at their best.

Where Close is ahead

Close passes structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented, and Salesforce does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.

It also holds adopt: self-service signup, no mandatory sales call and programmatic credential creation. Salesforce misses those.

And on operate, structured, predictable output, machine-readable errors, rate-limit behavior predictable and agent compatibility verified. Salesforce misses those.

Where Salesforce is ahead

Salesforce passes clear product positioning and public docs discoverable, and Close does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: official python sdk. Close misses it.

What neither does

Both fail llms-full.txt / full agent docs, mcp discoverable, authentication documented, fast time to first request, copyable quickstart, cli available, mcp integration available, retry behavior documented, idempotency support. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. Salesforce leads 80 to 53. Close misses clear product positioning, public docs discoverable, llms-full.txt / full agent docs, mcp discoverable; Salesforce misses llms-full.txt / full agent docs, mcp discoverable.

Understand is whether an agent can read the docs and work out how the API behaves before calling it. Close leads 92 to 23. Close misses authentication documented; Salesforce misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Close leads 60 to 35. Close misses fast time to first request, copyable quickstart, official python sdk, cli available, mcp integration available; Salesforce misses self-service signup, no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, cli available, mcp integration available.

Operate. Close leads 89 to 35. Close misses retry behavior documented, idempotency support; Salesforce misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Close does not publish a machine-readable starting price and has a free tier. Salesforce does not publish one with no free tier.

Signal by signal

Which to pick

Close clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Close and Salesforce. Alternatives to each: Close, Salesforce.

An agent can fetch this as data: POST /v1/compare {"slugs": ["close", "salesforce"]}