Adobe vs Letta
Letta scores higher on the AgentReady, 72/100 against 51/100. They differ on 12 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Adobe. Adobe products and services empower developers to create memorable digital experiences through developer creativity
Letta. Letta is an AI research lab in San Francisco building machines that learn.
Where Adobe is ahead
Adobe 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.
Where Letta is ahead
Letta passes public docs discoverable and llms.txt published, and Adobe 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, pricing understandable and limits / constraints documented. Adobe misses those.
And on adopt, self-service signup, agent-compatible signup flow, free trial or free allowance, fast time to first request and copyable quickstart. Adobe misses those.
Finally, on operate, structured, predictable output. Adobe misses 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 80. Adobe misses public docs discoverable, llms.txt published; Letta misses nothing.
Understand. Letta leads 38 to 31. Adobe misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Letta misses structured api reference, openapi / spec quality, 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. Letta leads 81 to 40. Adobe misses self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart; Letta misses no mandatory sales call, programmatic credential creation.
Operate. Letta leads 67 to 53. Adobe misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Letta misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.
Pricing
Adobe does not publish a machine-readable starting price. Letta starts at $0/mo and has a free tier.
| Adobe plans | Letta plans |
|---|---|
| - | Free $0 /month |
| - | Pro $20 /month |
| - | API Plan $20 /month |
| - | Teams Pro $20 /seat/month |
| - | Enterprise Custom |
Signal by signal
| Signal | Adobe | Letta |
|---|---|---|
| AgentReady | 51 | 72 |
| Discovery | 80 | 100 |
| Understanding | 31 | 38 |
| Adoption | 40 | 81 |
| Operability | 53 | 67 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Unknown |
| CLI | Yes | Yes |
| llms.txt | Unknown | Yes |
| Self-serve signup | Unknown | Yes |
| Free tier | Unknown | Yes |
Which to pick
Letta clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Adobe and Letta. Alternatives to each: Adobe, Letta.
An agent can fetch this as data: POST /v1/compare {"slugs": ["adobe", "letta"]}