Letta vs Replicate
Replicate scores higher on the AgentReady, 82/100 against 72/100. They differ on 11 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.
Replicate. Platform to run and fine-tune AI models, deploy custom models, and generate images, speech, music, and video via API
Where Letta is ahead
Letta passes agent-compatible signup flow, fast time to first request and copyable quickstart, and Replicate does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.
It also holds operate: agent compatibility verified. Replicate misses it.
Where Replicate is ahead
Replicate passes structured api reference, openapi / spec quality, request examples provided, response examples provided and errors and status codes documented, and Letta does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.
It also holds adopt: programmatic credential creation. Letta misses it.
And on operate, machine-readable errors. Letta misses it.
What neither does
Both fail no mandatory sales call, 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.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Replicate leads 100 to 38. Letta misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented; Replicate misses nothing.
Adopt. Letta leads 81 to 70. Letta misses no mandatory sales call, programmatic credential creation; Replicate misses no mandatory sales call, agent-compatible signup flow, fast time to first request, copyable quickstart.
Operate. Letta leads 67 to 59. Letta misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Replicate misses retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Letta starts at $0/mo and has a free tier. Replicate does not publish one and has a free tier.
| Letta plans | Replicate plans |
|---|---|
| Free $0 /month | - |
| Pro $20 /month | - |
| API Plan $20 /month | - |
| Teams Pro $20 /seat/month | - |
| Enterprise Custom | - |
Signal by signal
| Signal | Letta | Replicate |
|---|---|---|
| AgentReady | 72 | 82 |
| Discovery | 100 | 100 |
| Understanding | 38 | 100 |
| Adoption | 81 | 70 |
| Operability | 67 | 59 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Unknown | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Replicate clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Letta and Replicate. Alternatives to each: Letta, Replicate.
An agent can fetch this as data: POST /v1/compare {"slugs": ["letta", "replicate"]}