Exa vs Patronus
Exa scores higher on the AgentReady, 92/100 against 59/100. They differ on 14 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Exa. Exa is a custom search engine built for AIs, offering an API to search the largest index of public web and private information.
Patronus. Patronus AI is a frontier lab training the first Digital World Models.
Where Exa is ahead
Exa passes clear canonical domain and clear product positioning, and Patronus 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, authentication documented, request examples provided, response examples provided and errors and status codes documented. Patronus misses those.
And on adopt, programmatic credential creation and cli available. Patronus misses those.
Finally, on operate, structured, predictable output, machine-readable errors, rate-limit behavior predictable and agent compatibility verified. Patronus misses those.
Where Patronus is ahead
Patronus passes agent-compatible signup flow, and Exa does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.
What neither does
Both fail no mandatory sales call, 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. Exa leads 100 to 80. Exa misses nothing; Patronus misses clear canonical domain, clear product positioning.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Exa leads 100 to 46. Exa misses nothing; Patronus misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented.
Adopt. Exa leads 81 to 75. Exa misses no mandatory sales call, agent-compatible signup flow; Patronus misses no mandatory sales call, programmatic credential creation, cli available.
Operate. Exa leads 88 to 35. Exa misses retry behavior documented, idempotency support; Patronus misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Exa starts at $0 (free tier with credits) and has a free tier. Patronus starts at $0/mo and has a free tier.
| Exa plans | Patronus plans |
|---|---|
| - | Individual Free/Month |
| - | Base $25/Month |
| - | Enterprise Contact us for Pricing |
| - | Developer $10 / 1k small evaluator API calls; $20 / 1k large evaluator API calls; $10 / 1k eval explanations |
Signal by signal
| Signal | Exa | Patronus |
|---|---|---|
| AgentReady | 92 | 59 |
| Discovery | 100 | 80 |
| Understanding | 100 | 46 |
| Adoption | 81 | 75 |
| Operability | 88 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Unknown |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Exa clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Exa and Patronus. Alternatives to each: Exa, Patronus.
An agent can fetch this as data: POST /v1/compare {"slugs": ["exa", "patronus"]}