Treblle vs Unkey
Unkey scores higher on the AgentReady, 56/100 against 55/100. They differ on 8 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Treblle. Enterprise Runtime Intelligence Platform for API visibility, security, and governance.
Unkey. Unkey is a developer platform for modern APIs that unifies infrastructure, allowing developers to deploy APIs instantly, route traffic through global gateways, and understand usage in one place.
Where Treblle is ahead
Treblle passes mcp discoverable, and Unkey does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds adopt: agent-compatible signup flow and mcp integration available. Unkey misses those.
Where Unkey is ahead
Unkey passes llms.txt published, and Treblle 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 limits / constraints documented. Treblle misses those.
And on adopt, self-service signup and fast time to first request. Treblle misses those.
What neither does
Both fail llms-full.txt / full agent docs, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, no mandatory sales call, programmatic credential creation, 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. Treblle leads 87 to 80. Treblle misses llms.txt published, llms-full.txt / full agent docs; Unkey 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. Unkey leads 54 to 38. Treblle misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Unkey misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented.
Adopt. Treblle leads 60 to 55. Treblle misses self-service signup, no mandatory sales call, programmatic credential creation, fast time to first request; Unkey misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, mcp integration available.
Operate. Both sit at 35/100 here. Treblle misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Unkey misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Treblle starts at $233/mo with no free tier. Unkey starts at $5/mo and has a free tier.
| Treblle plans | Unkey plans |
|---|---|
| Core $233 / mo | Starter $5/mo |
| Growth Custom Pricing | Pro $25/mo |
| Enterprise Custom Pricing | Business Custom |
Signal by signal
| Signal | Treblle | Unkey |
|---|---|---|
| AgentReady | 55 | 56 |
| Discovery | 87 | 80 |
| Understanding | 38 | 54 |
| Adoption | 60 | 55 |
| Operability | 35 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Yes |
| llms.txt | No | Yes |
| Self-serve signup | No | Yes |
| Free tier | No | Yes |
Which to pick
Unkey clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Treblle and Unkey. Alternatives to each: Treblle, Unkey.
An agent can fetch this as data: POST /v1/compare {"slugs": ["treblle", "unkey"]}