Compare

Close vs Folk

Close scores higher on the AgentReady, 74/100 against 52/100. They differ on 15 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.

Folk. folk CRM captures the full context of your relationships in one beautifully simple CRM.

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 Folk 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: no mandatory sales call and programmatic credential creation. Folk misses those.

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

Where Folk is ahead

Folk passes 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 adopt: official python sdk and mcp integration available. Close misses those.

And on operate, retry behavior documented. Close misses it.

What neither does

Both fail clear product positioning, public docs discoverable, llms-full.txt / full agent docs, authentication documented, fast time to first request, copyable quickstart, cli available, 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. Folk leads 67 to 53. Close misses clear product positioning, public docs discoverable, llms-full.txt / full agent docs, mcp discoverable; Folk misses clear product positioning, public docs discoverable, llms-full.txt / full agent docs.

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; Folk misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

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

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

Pricing

Close does not publish a machine-readable starting price and has a free tier. Folk starts at $24/mo 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: Close and Folk. Alternatives to each: Close, Folk.

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