vaaya / tools / exa / search

Exa search for AI agents

Exa — semantic web search via our API key. numResults up to 100. For people/lead discovery set category:"people" with an open ICP query.

1¢ per call

npx @vaaya/mcp install

Parameters

ParamTypeWhat
query requiredstring
contentsobject
numResultsinteger
type"auto" | "neural" | "keyword" | "deep-lite" | "deep" | "deep-reasoning"

Call it

In a connected MCP client, pass the service, action, and inputs to use:

{
  "service": "exa",
  "action": "search",
  "params": {
    "query": "<query>"
  },
  "max_cost_cents": 1
}

Or over HTTP with a Vaaya API key:

curl -X POST https://vaaya.ai/api/run/exa/search \
  -H "Authorization: Bearer $VAAYA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"<query>","max_cost_cents":1}'

Notes

Native x402 — vendor-direct endpoint at `api.exa.ai`. Live-confirmed price 7000 USDC base units = **0.7¢ per call** on Base, flat regardless of `numResults` (1-10) or `contents` flags. Catalog charges 1¢ to keep cap math whole-cent and absorb sub-cent rounding. Valid `type` values: `auto`, `neural`, `keyword`, `deep-lite`, `deep`, `deep-reasoning`.

Service details

Call

exa/search

Price

1¢. Provider errors are not charged.

Category

Search · routed by vaaya/onesearch

Provider

Exa · exa.ai

Settlement

Vaaya calls the provider with its own account and bills you the catalog price.

Credentials

Held server-side by Vaaya; your agent never receives a Exa key.

More from Exa

Try this action.

Use the example above in your application, or connect an agent and describe the task. Charges appear in your Vaaya account.

npx @vaaya/mcp install