OpenRouter

Latest Audit Result

OpenRouter’s public SDKs/docs confirm the declared capability coverage at the public-interface level: Exa-backed web search uses auto-style search and returns text/snippet content via OpenRouter annotations/server-tool outputs. No public repository exposes OpenRouter’s private direct Exa HTTP implementation, and a live OpenRouter probe was blocked by 402 insufficient credits, so exact backend calls to `/search`, `/contents`, `/findSimilar`, or `/answer` cannot be fully verified from available materials. Public source/docs show no confirmed use of deprecated Exa API features (`/research`, `resolvedSearchType`, `highlightScores`, `startCrawlDate`, `endCrawlDate`).

Missing Features (2)

• Migrate OpenRouter-facing documentation/client guidance away from the deprecated OpenRouter `plugins: [{ id: "web" }]` / `:online` path toward the `openrouter:web_search` server tool.
• Obtain OpenRouter internal backend source or credited OpenRouter API access if exact direct Exa endpoint/payload verification is required; public SDKs only expose OpenRouter request shapes, not the private Exa HTTP calls.