Talk about your next project
Exa case study

The lesson

Lead with the integration outcome, then show the exact tool interface that made the customer story real.

The move

The story opens with the OpenRouter name, the title “How OpenRouter gives 400+ models web search with Exa,” and three metrics: “73M Search queries to date,” “400+ Models connected,” and “25T Tokens first week of May.” A company panel lists OpenRouter’s industry, size, and API, followed by three summary lines and a quote from Alex Atallah. The body moves through “About OpenRouter,” “The Challenge,” “The Solution,” “Why Exa,” and “Results,” with short feature blocks such as “One tool for every model,” “Agentic search loops,” “Exa highlights and citations,” “Adaptive context,” “Domain controls,” and “Unified usage tracking.” It ends with “Try it on OpenRouter,” showing the exact tool call, then a product CTA for Exa APIs.

Why it works

  • Our readThe first screen gives the customer, the use case, and the scale of usage before asking the reader to follow the technical explanation.
  • Our readThe CEO quote explains Exa’s role in OpenRouter’s own words, which makes the story about model grounding rather than a generic search API claim.
  • Our readThe tool-call example turns the case study into proof a developer can recognize, because the integration is shown as a concrete request shape.

What not to copy

Don't copy OpenRouter's model marketplace, the openrouter:web_search tool name, or Exa's highlights language. Keep the structure of metric-led proof, customer quote, problem, implementation details, product fit, results, and a concrete next step.

More from Exa

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.