Exa `contents` for AI agents

Name: Exa contents for AI agents
Brand: Exa

Exa — retrieve content for URLs or document IDs via our API key. Charges 0.1¢ per (url or id) × content field requested.

varies by params per call

npx @vaaya/mcp install

Parameters

Param	Type	What
`highlights`	`boolean \| object`
`ids`	`string[]`
`summary`	`boolean \| object`
`text`	`boolean`
`urls`	`string[]`

Call it

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

{
  "service": "exa",
  "action": "contents",
  "params": {},
  "max_cost_cents": 100
}

Or over HTTP with a Vaaya API key:

curl -X POST https://vaaya.ai/api/run/exa/contents \
  -H "Authorization: Bearer $VAAYA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"max_cost_cents":100}'

Notes

Native x402 — vendor-direct endpoint at `api.exa.ai`. Live-confirmed pricing: **0.1¢ per (url or id) × per content field requested** (`text`, `highlights`, `summary`). Examples: 1 URL with `text` = 0.1¢; 10 URLs with `text` = 1.0¢; 1 URL with all three fields = 0.3¢; 10 URLs with all three fields = 3.0¢. The dispatcher prices each call dynamically, ceiling-rounded to whole cents. Both `urls` and `ids` are arrays of strings; at least one must be non-empty.

The facts

Call

exa/contents

Price

varies by params. 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.