Exa vs Lmstudio
Exa scores higher on the AgentReady, 92/100 against 65/100. They differ on 15 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Exa. Exa is a custom search engine built for AIs, offering an API to search the largest index of public web and private information.
Lmstudio. LM Studio is a platform for running local LLMs (large language models) with a focus on privacy and offline operation.
Where Exa is ahead
Exa passes openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented, and Lmstudio 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, fast time to first request and copyable quickstart. Lmstudio misses those.
And on operate, structured, predictable output, machine-readable errors, rate-limit behavior predictable and observable execution. Lmstudio misses those.
Where Lmstudio is ahead
Lmstudio passes no mandatory sales call and agent-compatible signup flow, and Exa does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.
What neither does
Both fail retry behavior documented, idempotency support. 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. Exa leads 100 to 38. Exa misses nothing; Lmstudio misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Exa leads 81 to 80. Exa misses no mandatory sales call, agent-compatible signup flow; Lmstudio misses programmatic credential creation, fast time to first request, copyable quickstart.
Operate. Exa leads 88 to 41. Exa misses retry behavior documented, idempotency support; Lmstudio misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution.
Pricing
Exa starts at $0 (free tier with credits) and has a free tier. Lmstudio starts at $0 and has a free tier.
| Exa plans | Lmstudio plans |
|---|---|
| - | Free $0 |
| - | Pay as you go Cloud credits |
Signal by signal
| Signal | Exa | Lmstudio |
|---|---|---|
| AgentReady | 92 | 65 |
| Discovery | 100 | 100 |
| Understanding | 100 | 38 |
| Adoption | 81 | 80 |
| Operability | 88 | 41 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Exa clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Exa and Lmstudio. Alternatives to each: Exa, Lmstudio.
An agent can fetch this as data: POST /v1/compare {"slugs": ["exa", "lmstudio"]}