Adobe vs Last9
Adobe scores higher on the AgentReady, 51/100 against 48/100. They differ on 8 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
Last9. Last9 is an observability platform for logs, metrics, and traces.
Where Adobe is ahead
Adobe passes search discoverable, and Last9 does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: structured api reference. Last9 misses it.
And on adopt, cli available. Last9 misses it.
Finally, on operate, observable execution. Last9 misses it.
Where Last9 is ahead
Last9 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 adopt: agent-compatible signup flow and copyable quickstart. Adobe misses those.
What neither does
Both fail openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, structured, predictable output, 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. Last9 leads 87 to 80. Adobe misses public docs discoverable, llms.txt published; Last9 misses search discoverable.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Adobe leads 31 to 15. Adobe misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Last9 misses structured api reference, openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Last9 leads 50 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; Last9 misses self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, cli available.
Operate. Adobe leads 53 to 41. Adobe misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Last9 misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution.
Pricing
Adobe does not publish a machine-readable starting price. Last9 does not publish one.
Signal by signal
| Signal | Adobe | Last9 |
|---|---|---|
| AgentReady | 51 | 48 |
| Discovery | 80 | 87 |
| Understanding | 31 | 15 |
| Adoption | 40 | 50 |
| Operability | 53 | 41 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Unknown |
| CLI | Yes | Unknown |
| llms.txt | Unknown | Yes |
| Self-serve signup | Unknown | Unknown |
| Free tier | Unknown | Unknown |
Which to pick
Signal counts are level here, so fit and price decide it. Full profiles: Adobe and Last9. Alternatives to each: Adobe, Last9.
An agent can fetch this as data: POST /v1/compare {"slugs": ["adobe", "last9"]}