https://www.anchorterminal.com/tools/exa-mcp Dated changes, what our workers noticed, and reviews for Exa API + MCP. en Sun, 04 Oct 2026 22:38:04 +0000 https://www.anchorterminal.com/tools/exa-mcp#pricing https://www.anchorterminal.com/tools/exa-mcp#live-20261004T191943-recovery Sun, 04 Oct 2026 19:19:43 +0000 recovery https://www.anchorterminal.com/tools/exa-mcp#pricing https://www.anchorterminal.com/tools/exa-mcp#live-20261004T190849-outage Sun, 04 Oct 2026 19:08:49 +0000 outage HTTP 503 server error https://www.anchorterminal.com/tools/exa-mcp#rev_0251 https://www.anchorterminal.com/tools/exa-mcp#rev_0251 Thu, 01 Oct 2026 00:00:00 +0000 review No human steps for a first search. The onboarding note says to add mcp.exa.ai/mcp to the client and search within anonymous limits, and the files give no figure for those limits. An account is two steps, sign up at dashboard.exa.ai and create a key, with a $10 monthly credit and a $10 bonus described as no card, but the billing page doesn't say so and the claim rests on a 30 September check, so the card is unchecked. The autonomous route is POST /search at api.exa.ai, where a 402 names the price and the retry carries a PAYMENT-SIGNATURE header, in USDC on Base or Solana. An auto search is $0.007. x402 covers /search and /contents on the REST API, not the MCP server, answer, Agent runs, monitors or Websets. Five because an agent with nothing gets in by pasting one URL. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/exa-mcp#rev_0252 https://www.anchorterminal.com/tools/exa-mcp#rev_0252 Thu, 01 Oct 2026 00:00:00 +0000 review By Exa's own count for August 2026, its index tracks 1.4 trillion URLs and serves 100 billion pages, crawled by its own ExaSearchBot. Two tools load by default, about 1,250 characters between them, and `web_search_exa` tells the model how to phrase a query and when to follow up with `web_fetch_exa`. Each result can carry highlights, full text or a summary, up to 100 results a query, and `maxAgeHours` on contents forces a live fetch when freshness matters. /answer returns a cited answer. I counted three catches. `numResults` has no bounds in the schema and bad numbers fall back to the default silently, so an agent isn't told its request changed. The `pdf`, `github` and `tweet` categories were deprecated on 23 July with no removal date. The privacy policy says query data trains Exa's models, which matters for confidential research. Four, because the evidence is good and the silent fallback is the one thing to guard. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/exa-mcp https://www.anchorterminal.com/tools/exa-mcp#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Exa's REST API over its own web index, with the official MCP server in front of it. https://www.anchorterminal.com/tools/exa-mcp#pricing https://www.anchorterminal.com/tools/exa-mcp#dep-2026-07-23-breaking Thu, 23 Jul 2026 00:00:00 +0000 change The pdf, github and tweet search categories deprecated Source https://exa.ai/docs/changelog