Compare

Exa vs OpenRouter

Exa scores higher on the AgentReady, 92/100 against 81/100. They differ on 20 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.

OpenRouter. OpenRouter is a unified interface for AI models that provides access to hundreds of AI models through a single API endpoint.

Where Exa is ahead

Exa passes search discoverable, public docs discoverable and mcp discoverable, and OpenRouter does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: openapi / spec quality, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented. OpenRouter misses those.

And on adopt, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available and mcp integration available. OpenRouter misses those.

Finally, on operate, canonical workflow succeeds, structured, predictable output, machine-readable errors, rate-limit behavior predictable and observable execution. OpenRouter misses those.

What neither does

Both fail no mandatory sales call, 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.

Discover. Both sit at 100/100 here. Exa misses nothing; OpenRouter misses search discoverable, public docs discoverable, mcp discoverable.

Understand. Exa leads 100 to 92. Exa misses nothing; OpenRouter misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. OpenRouter leads 88 to 81. Exa misses no mandatory sales call, agent-compatible signup flow; OpenRouter misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, cli available, mcp integration available.

Operate is whether an agent can run against it in production and recover when a call fails. Exa leads 88 to 44. Exa misses retry behavior documented, idempotency support; OpenRouter misses canonical workflow succeeds, 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. OpenRouter does not publish one and has a free tier.

Signal by signal

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 OpenRouter. Alternatives to each: Exa, OpenRouter.

An agent can fetch this as data: POST /v1/compare {"slugs": ["exa", "openrouter"]}