Compare

Attio vs Close

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

What each one is

Attio. Attio is the CRM that builds pipeline, advances deals, and grows accounts around the clock.

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.

Where Attio is ahead

Attio passes clear product positioning, llms-full.txt / full agent docs and mcp 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 understand: authentication documented. Close misses it.

And on adopt, mcp integration available. Close misses it.

Where Close is ahead

Close passes search discoverable and clear canonical domain, and Attio does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: openapi / spec quality, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented. Attio misses those.

And on adopt, no mandatory sales call, programmatic credential creation and official typescript sdk. Attio misses those.

Finally, on operate, canonical workflow succeeds, structured, predictable output, machine-readable errors, rate-limit behavior predictable and observable execution. Attio misses those.

What neither does

Both fail public docs discoverable, fast time to first request, copyable quickstart, official python sdk, cli 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 is whether an agent can find the product at all without being told it exists. Attio leads 92 to 53. Attio misses search discoverable, clear canonical domain, public docs discoverable; Close misses clear product positioning, public docs discoverable, llms-full.txt / full agent docs, mcp discoverable.

Understand. Close leads 92 to 83. Attio misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Close misses authentication documented.

Adopt. Attio leads 88 to 60. Attio misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available; Close misses fast time to first request, copyable quickstart, official python sdk, cli available, mcp integration available.

Operate. Both sit at 89/100 here. Attio misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution; Close misses retry behavior documented, idempotency support.

Pricing

Attio does not publish a machine-readable starting price and has a free tier. Close does not publish one and has a 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: Attio and Close. Alternatives to each: Attio, Close.

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