Exa

Exa combines search with page retrieval, similarity discovery, and research runs through APIs designed for AI workloads. Verified capabilities from the fetched vendor homepage and pricing page include neural search, content retrieval, research API, similar-page discovery, MCP server. Practical uses include RAG grounding, company research, sourced web research. Pricing visible during this run was: Starter (Free): $20 signup plus $10 monthly credits; Search API ($7/1,000 requests): Displayed rate; Research ($0.012–$1.00/run): Varies by task; Enterprise (Contact sales): Custom terms. MCP compatibility is prominent: Exa includes MCP server access so compatible assistants can search and retrieve content. For buyers, the main question is whether the service replaces infrastructure the team would otherwise maintain or adds a useful control layer around existing systems. Builders should test authentication boundaries, rate limits, failure recovery, latency, data retention, and total cost under realistic traffic. Business owners should confirm which governance, collaboration, security, and support capabilities belong to each plan because packaging can change separately from the core product. A pilot should use one representative workflow and measure completion rate, output quality, operator review time, and combined vendor plus model spend. The fetched pages establish the claims and prices recorded here, but do not guarantee that every feature is available in every region, plan, connector, or deployment mode. Thin, redirected, or script-heavy pricing pages are explicitly marked for manual verification. Before production rollout, teams should also review concurrency, audit exports, identity-provider support, compliance requirements, and the process for removing or migrating stored data. This profile is written for builders and business users: it explains what the product does, where it fits, and what must still be validated without assuming unlisted capabilities.