Patronus vs Vespa
Patronus scores higher on the AgentReady, 59/100 against 56/100. They differ on 6 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Patronus. Patronus AI is a frontier lab training the first Digital World Models.
Vespa. Vespa.ai develops the Vespa AI Search Platform, a distributed serving engine that unifies retrieval, ranking, machine learning inference, and real-time serving for business-critical AI applications.
Where Patronus is ahead
Patronus passes mcp discoverable, and Vespa 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. Vespa misses those.
Where Vespa is ahead
Vespa 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 adopt: cli available. Patronus misses it.
What neither does
Both fail openapi / spec quality, authentication documented, 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. Vespa leads 87 to 80. Patronus misses clear canonical domain, clear product positioning; Vespa misses mcp discoverable.
Understand. Both sit at 46/100 here. Patronus misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented; Vespa misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented.
Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Patronus leads 75 to 55. Patronus misses no mandatory sales call, programmatic credential creation, cli available; Vespa misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, mcp integration available.
Operate. Both sit at 35/100 here. Patronus misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Vespa misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Patronus starts at $0/mo and has a free tier. Vespa starts at $0.05/hour with no free tier.
| Patronus plans | Vespa plans |
|---|---|
| Individual Free/Month | Startup vCPU $0.05/hour, Memory GB $0.005/hour, Disk GB $0.0002/hour, GPU Memory GB $0.03/hour |
| Base $25/Month | Basic vCPU $0.1/hour, Memory GB $0.01/hour, Disk GB $0.0004/hour, GPU Memory GB $0.07/hour |
| Enterprise Contact us for Pricing | Commercial vCPU $0.145/hour, Memory GB $0.0145/hour, Disk GB $0.0005/hour, GPU Memory GB $0.1/hour |
| Developer $10 / 1k small evaluator API calls; $20 / 1k large evaluator API calls; $10 / 1k eval explanations | Enterprise vCPU $0.18/hour, Memory GB $0.018/hour, Disk GB $0.0007/hour, GPU Memory GB $0.125/hour |
| - | Self Managed Contact Sales |
Signal by signal
| Signal | Patronus | Vespa |
|---|---|---|
| AgentReady | 59 | 56 |
| Discovery | 80 | 87 |
| Understanding | 46 | 46 |
| Adoption | 75 | 55 |
| Operability | 35 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Yes | Yes |
| CLI | Unknown | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | No |
Which to pick
Signal counts are level here, so fit and price decide it. Full profiles: Patronus and Vespa. Alternatives to each: Patronus, Vespa.
An agent can fetch this as data: POST /v1/compare {"slugs": ["patronus", "vespa"]}