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

Param	Type	What
`query` required	`string`
`contents`	`object`
`numResults`	`integer`
`type`	`"auto" \| "neural" \| "keyword" \| "deep-lite" \| "deep" \| "deep-reasoning"`

Call it

From any MCP client with Vaaya connected, one use call:

{
  "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`.

The facts

Call

exa/search

Price

1¢. Charged only on success.

Pillar

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.

Give your agents this call.

Connect Vaaya once, then describe the outcome or call it directly. Paid per call, from one balance.