Exa vs Recall
Side-by-side trajectory, velocity, and editorial themes.
Exa is pushing past search into autonomous web-research agents.
Exa has moved beyond its search-and-retrieval API into agentic territory. The headline change is Exa Agent — a research agent built on Exa's index and reachable via API — now joined by MCP availability for Agent and Connect. The underlying search product keeps maturing in parallel: auto-routing, people and company search, markdown-native content, and instant results.
The arc runs from primitives to products: a fast index, then specialized verticals (people, companies), now an agent that composes them into end-to-end research. Bringing Agent and Connect to MCP signals Exa wants to be a retrieval backend inside other agent stacks, not just a standalone API.
Expect Exa to deepen the agent layer — structured research outputs and monitoring already appear in the changelog — and to lean on MCP distribution to embed inside third-party agents rather than compete for end users directly.
After Recall 2.0, the second-brain iterates fast on sources, voice, and control
Since April's Recall 2.0 relaunch — agentic chat, an API and MCP, and the Max tier — the product has been in rapid iteration. It has widened what it can ingest (Instagram, LinkedIn, Apple News, text/Markdown), added Listen Mode voice playback, and now Custom Personas that pin how the AI behaves. The consistent thesis is knowledge-first AI: your saved sources come before the open web.
Recall is layering reach and control onto its chat: more sources in, more ways to steer the AI (personas, multi-step actions), and more model choice (Opus 4.8, GPT-5.5). Release notes point toward public profiles, sharing, and a write API as the next expansion beyond personal capture.
Based on the roadmap notes threaded through these releases, expect public Recall profiles and shared collections, plus a write/bulk-ingest API, to be the next headline moves.
See more alternatives to Exa →
See more alternatives to Recall →