Exa Search
$0.02/call
100+ calls
AI-powered semantic search, find-similar, and content extraction
Connect Exa Search tools
Cursor
Claude Code
Claude Desktop
Windsurf
VS Code
Cline
Roo Code
ChatGPT
Gemini CLI
Amazon Q
Goose
Augment
n8n
API / cURL
AI SDK
TypeScript SDK
{
"mcpServers": {
"exa": {
"url": "https://exa.mcp.xpay.sh/mcp?key=YOUR_API_KEY"
}
}
}Or connect all tools
Access all tools (including Exa Search) through a single MCP connection.
{
"mcpServers": {
"xpay": {
"url": "https://mcp.xpay.sh/mcp?key=YOUR_API_KEY"
}
}
}Agent Discovery
Machine-readable catalogs for LLM agents and automation.
curl https://xpay.tools/llms.txt
curl https://xpay.tools/agents.txt
curl https://xpay.tools/skill.md
Pricing
Pay per tool call. No subscriptions.
2 Exa Search tools availableAbout Exa Search
Exa Search on xpay — AI-powered semantic search without the signup
Exa Search is a semantic search engine built for AI agents. Instead of keyword matching, it understands meaning and intent, making it ideal for finding relevant content, extracting full pages, and discovering similar resources. Developers typically reach for Exa when they need clean, AI-ready search results or when they want to read webpage content programmatically without parsing HTML themselves.
On xpay, you call Exa Search's tools directly through MCP—no Exa Search account required, no monthly subscription, and you pay only for what you use.
What's available
web_search_exa($0.02/call) — Semantic search across the web. Returns clean, ranked results with titles, URLs, and excerpts. Built for finding current information, news, facts, people, companies, or answering questions about any topic.web_fetch_exa($0.02/call) — Read a webpage's full content as clean markdown. Use this afterweb_search_exawhen highlights are insufficient, or to extract content from any known URL. Supports batch operations.
When Exa Search is the right tool
- You need semantic search rather than keyword-based results—Exa understands intent and meaning.
- Your agent must find current information (news, facts, recent events) that's not in its training data.
- You want to extract full webpage content as structured markdown without parsing HTML.
- You're building a research assistant or fact-checking agent that needs live web access.
- You need find-similar capabilities to discover related content or resources.
- You want clean, AI-ready output without boilerplate, ads, or navigation clutter.
When to choose something else
- If you only need keyword-based search, a simpler API like Google Custom Search or Bing may be cheaper and sufficient.
- If your use case is social media monitoring or sentiment analysis, specialized tools (e.g., Brandwatch, Sprout Social) are better fits.
- If you need real-time stock prices, weather, or sports scores, use dedicated APIs for those verticals instead.
- If you're doing large-scale web crawling or SEO analysis, consider headless browser tools or dedicated crawlers.
- If your queries are highly domain-specific (medical, legal, academic), a fine-tuned or specialized search engine may outperform general semantic search.
Pricing snapshot
| Tool | Price per call |
|---|---|
web_search_exa | $0.02 |
web_fetch_exa | $0.02 |
Both tools are priced identically on xpay. You're billed per invocation; no minimum spend or subscription.
Quickstart
Install the Exa Search MCP endpoint in Claude Code:
claude mcp add --transport http exa "https://exa.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"
Replace YOUR_XPAY_KEY with your xpay API key (get it free at https://xpay.tools after email or Google signup).
Once connected, Claude Code will have access to web_search_exa and web_fetch_exa by their native names. Simply ask Claude to search the web or fetch a page, and it will invoke the tools automatically.
For Cursor, Windsurf, Cline, or VS Code (Copilot): Add this entry to your mcp.json file:
{
"mcpServers": {
"exa": {
"url": "https://exa.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"
}
}
}
To use multiple xpay providers in one connection, use the unified endpoint instead:
claude mcp add --transport http xpay "https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"
With the unified endpoint, you'll also have access to xpay_discover(), xpay_details(), and xpay_run() meta-tools to browse and invoke any xpay provider.
Why route Exa Search through xpay?
- No Exa Search signup — xpay holds the provider credentials. You authenticate once with your xpay key and gain access to Exa Search immediately.
- Pay-per-call, no subscription — You're charged only for the calls you make ($0.02 each). No monthly fees, no unused credits.
- MCP-native integration — Exa Search is exposed as a standard MCP endpoint. Works with Claude Code, Cursor, Windsurf, Cline, and any MCP-compatible agent.
- Unified billing across providers — If you use multiple APIs (Tavily, Apollo, Perplexity, etc.), xpay consolidates billing into one invoice and one API key.
- Instant activation — Start using Exa Search within seconds of signing up for xpay. No waiting for approval or API key generation from Exa directly.
Frequently Asked Questions
Exa Search is an AI-powered semantic search engine. Unlike traditional keyword-based search, it understands the meaning and intent behind queries, returning cleaner, more relevant results. It also offers content extraction (reading full webpages as markdown) and find-similar capabilities. It's designed for AI agents and developers who need live web access and structured, AI-ready output.
Both `web_search_exa` and `web_fetch_exa` cost $0.02 per call on xpay. You're billed only for the calls you make—no subscription, no minimum spend. New xpay accounts receive $5 in free credit to try it out.
No. xpay handles the Exa Search credentials on your behalf. You sign up once at xpay.tools (with email or Google), get an API key, and immediately have access to Exa Search through MCP. You never create an Exa Search account or manage separate API keys.
Use Exa Search when you need semantic web search (finding relevant content by meaning, not keywords), extracting full webpage content as markdown, discovering current information (news, facts, recent events), or building research and fact-checking agents. It's ideal for any AI agent that needs live, clean web access.
Run: `claude mcp add --transport http exa "https://exa.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"` (replace `YOUR_XPAY_KEY` with your xpay API key from https://xpay.tools). Once connected, Claude Code will have access to `web_search_exa` and `web_fetch_exa` and can invoke them automatically when you ask it to search or fetch a page.
Add an entry to your `mcp.json` file: `{ "mcpServers": { "exa": { "url": "https://exa.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY" } } }`. Replace `YOUR_XPAY_KEY` with your xpay API key. Restart your editor, and the tools will be available to your agent.
Alternatives include Tavily Search (keyword + semantic search), Google Custom Search (keyword-based), Bing Search API, and Perplexity (AI-powered search with citations). Choose Tavily or Perplexity if you want AI-enhanced results; choose Google or Bing if keyword search is sufficient. Exa stands out for semantic search quality and clean, AI-ready output.
Yes. You can install the per-provider Exa endpoint (`https://exa.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY`) for Exa alone, or use the unified xpay endpoint (`https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY`) to access all xpay providers (Exa, Tavily, Apollo, Perplexity, etc.) through one MCP connection. All calls are billed to your single xpay account.

