Compare

Cerbos vs Kinde

Kinde scores higher on the AgentReady, 54/100 against 46/100. They differ on 9 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Cerbos. Authorization management platform for applications, APIs, AI agents, MCP servers, services, and workloads.

Kinde. Modern auth and billing for engineers.

Where Cerbos is ahead

Cerbos passes copyable quickstart, official typescript sdk and official python sdk, and Kinde does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.

Where Kinde is ahead

Kinde passes clear canonical domain, and Cerbos 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 and pricing understandable. Cerbos misses those.

And on adopt, self-service signup, no mandatory sales call and free trial or free allowance. Cerbos misses those.

What neither does

Both fail structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, agent-compatible signup flow, programmatic credential creation, fast time to first request, cli available, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. 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. Kinde leads 100 to 93. Cerbos misses clear canonical domain; Kinde misses nothing.

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

Adopt. Kinde leads 48 to 40. Cerbos misses self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, free trial or free allowance, fast time to first request, cli available; Kinde misses agent-compatible signup flow, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available.

Operate. Both sit at 35/100 here. Cerbos misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Kinde misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Cerbos does not publish a machine-readable starting price. Kinde starts at $25/mo and has a free tier.

Signal by signal

Which to pick

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

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