$HEADLESS SYSTEMS
03 / Scorecard / Search & Vector DBs

Exa

B
Headless Index
63/100
denominator 40
JAIRF
N/A
Verified
AUG 20, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Exa earns Band B in the Search & Vector DBs category of The Headless Index, with a thesis-fit score of 63/100. Its strongest dimension is MCP and agent posture (20/20); its weakest scored dimension is schema observability (5/20). No public OpenAPI specification was found when Exa was scored, which limits how far an agent can go without human integration work.

Editorial verdict
Exa is solidly built for programmatic consumption. The Headless Index thesis-fit score of 63/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Exa lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. On API-first posture, the structured collectors did not surface an OpenAPI spec, GraphQL endpoint, or SDK ecosystem strong enough to score this criterion automatically. Editorial follow-up should confirm whether an API spec exists behind authentication or in unindexed documentation.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at docs.exa.ai. Schema discoverability is good.[2] An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: On headless operability, the docs crawl did not produce topic coverage sufficient to score programmatic setup, billing, teams, schema, or CLI workflows. A targeted AI review pass should visit the vendor's docs index and confirm what programmatic surfaces actually exist.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Exa publishes an official MCP server, exa-labs/exa-mcp-server (over 5,000 stars, committed to the day before collection), so it is maintained and sits in the top band. Among the most agent-native search products.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: Exa can be operated by agents for the majority of practical workflows. The closest thing to a gap is schema observability[5], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intentUnknown
Unknown

Exa is semantic web search API designed for AI agents. REST API for search, find similar, get contents, and find sources. SDKs in Python and Node. Strong positioning in agent-search use cases (Anthropic's Claude, OpenAI Operator, etc.).

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPI specNot found across 34 probe paths
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • −SDKs maintainedNone detected in vendor org
cite (3)
  • openapi.probes_tried@2026-05-21
  • graphql.probes_tried@2026-05-21
  • github.sdks@2026-05-21
Headless operationUnknown
Unknown

Search queries, content retrieval, and similar-page discovery are programmable. The Exa dashboard handles billing and API key management.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedNo OpenAPI spec; operations count unknown
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-21
  • docs.pages_crawled@2026-05-21
  • docs.pages_crawled@2026-05-21
  • docs.topics_found.setup@2026-05-21
  • docs.topics_found.billing@2026-05-21
  • docs.topics_found.teams@2026-05-21
  • docs.topics_found.cli@2026-05-21
  • docs.topics_found.schema@2026-05-21
MCP & agent posture20/20
scored

Exa publishes an official MCP server, exa-labs/exa-mcp-server (over 5,000 stars, committed to the day before collection), so it is maintained and sits in the top band. Among the most agent-native search products.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +Official MCP serverhttps://github.com/exa-labs/exa-mcp-server (over 5,000 stars as observed 2026-10-13, last commit 2026-05-20, one day before collection)
  • −Community MCP serversNone found
  • −Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (2)
  • mcp.official_server.url@2026-05-21
  • github.sdks@2026-05-21
Schema observability5/20
scored

REST documented at docs.exa.ai. Schema discoverability is good.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPINot discovered across 34 standard probe paths
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (2)
  • openapi.probes_tried@2026-05-21
  • graphql.probes_tried@2026-05-21
Webhooks & eventsUnknown
Unknown

Webhook delivery is not central; the product is synchronous search.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-21
JAIRF · 6 dimensions
JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Powered by JAIRF v1.0.0 by Jentic

Band rationale:B band: JAIRF=N/A HeadlessIndex=63

04 / Embed

Show Exa's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

FAQ

Exa and agent readiness

Is Exa agent-ready?
Exa scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is schema observability.
Does Exa publish an OpenAPI spec?
No published OpenAPI specification was found when Exa was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Exa's Headless Index score?
Exa scores 63/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.