Letta vs Vespa
Letta scores higher on the AgentReady, 72/100 against 56/100. They differ on 7 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Letta. Letta is an AI research lab in San Francisco building machines that learn.
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 Letta is ahead
Letta 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 understand: authentication documented. Vespa misses it.
And on adopt, agent-compatible signup flow and mcp integration available. Vespa misses those.
Finally, on operate, structured, predictable output and agent compatibility verified. Vespa misses those.
Where Vespa is ahead
Vespa passes structured api reference, and Letta does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.
What neither does
Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, no mandatory sales call, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. 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. Letta leads 100 to 87. Letta misses nothing; Vespa misses mcp discoverable.
Understand. Vespa leads 46 to 38. Letta misses structured api reference, openapi / spec quality, 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. Letta leads 81 to 55. Letta misses no mandatory sales call, programmatic credential creation; Vespa misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, mcp integration available.
Operate is whether an agent can run against it in production and recover when a call fails. Letta leads 67 to 35. Letta misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Vespa misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Letta starts at $0/mo and has a free tier. Vespa starts at $0.05/hour with no free tier.
| Letta plans | Vespa plans |
|---|---|
| Free $0 /month | Startup vCPU $0.05/hour, Memory GB $0.005/hour, Disk GB $0.0002/hour, GPU Memory GB $0.03/hour |
| Pro $20 /month | Basic vCPU $0.1/hour, Memory GB $0.01/hour, Disk GB $0.0004/hour, GPU Memory GB $0.07/hour |
| API Plan $20 /month | Commercial vCPU $0.145/hour, Memory GB $0.0145/hour, Disk GB $0.0005/hour, GPU Memory GB $0.1/hour |
| Teams Pro $20 /seat/month | Enterprise vCPU $0.18/hour, Memory GB $0.018/hour, Disk GB $0.0007/hour, GPU Memory GB $0.125/hour |
| Enterprise Custom | Self Managed Contact Sales |
Signal by signal
| Signal | Letta | Vespa |
|---|---|---|
| AgentReady | 72 | 56 |
| Discovery | 100 | 87 |
| Understanding | 38 | 46 |
| Adoption | 81 | 55 |
| Operability | 67 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Unknown | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | No |
Which to pick
Letta clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Letta and Vespa. Alternatives to each: Letta, Vespa.
An agent can fetch this as data: POST /v1/compare {"slugs": ["letta", "vespa"]}