Skip to main content
Agents pay Exa with a credit card via Nevermined’s x402 card-delegation scheme. Each $7 purchase returns an Exa API key with $7 of Exa credits.
Use this Nevermined plan ID:
27800462147494506865542649899724877617306579171265399959488097895839186996870
This plan runs on Nevermined’s live environment (live-prefixed API keys). The purchase is for API credits, not for a single search request.
For a first-time Nevermined payer, POST /team-management/nevermined/purchase-key provisions a new Exa API key and adds $7 of credits. If the key runs out, mint a fresh x402 token with the same delegation and call the same endpoint again. Exa returns the same API key with another $7 of credits added.

Buy a key

  • Cost: $7 per purchase, charged to the card behind the delegation referenced by the x402 token.
  • Response (new payer): { status: "ok", apiKey: "…", expiresAt: null } — a new Exa API key with $7 of credits.
  • Response (returning payer): { status: "ok", apiKey: "…", expiresAt: null } — the same Exa API key with $7 more credits.
  • Response (replayed token): cached result, no new charge.
  • Missing/invalid signature: 402 Payment Required with payment requirements in the body.

How it works

The payment side is handled by Nevermined; Exa only sees the signed x402 token.
  1. One-time setup (by the card owner): enroll a card at nevermined.app, create a delegation on it (the spending permission: the owner sets a limit and duration, and can scope it to a specific API key), and issue a Nevermined API key for the agent.
  2. The agent finds its delegation. The Nevermined SDK lets the agent discover the delegations its key can spend from and pick one with enough remaining budget (at least $7). If none exists, the owner creates one in the dashboard, or a fully autonomous agent can create one through the SDK within the card’s limits.
  3. The agent mints an x402 access token for the plan ID above, on the card-delegation scheme, referencing the delegation by ID. Delegations must exist before minting; tokens cannot create them on the fly.
  4. The agent POSTs the token to the endpoint above in the payment-signature header and receives the Exa API key from the response.
  5. The key works immediately against the standard Exa Search API.
For the complete agent-ready walkthrough (SDK methods, parameters, delegation discovery and creation, troubleshooting), follow Nevermined’s Exa integration guide: nevermined.ai/docs/integrations/exa (agents: fetch nevermined.ai/docs/integrations/exa.md).

What $7 buys

Credits are consumed at standard Exa API pricing. At current rates, $7 of credits covers roughly: Search requests include text and highlights for up to 10 results. Extra results beyond 10 and AI summaries are billed separately.
For full pricing details, see Exa pricing.

When the key runs out

Exa returns HTTP 402 on the regular API endpoints once the API key’s credits are exhausted:
Mint a fresh x402 token with the same plan ID and delegation, then POST it again to the same /purchase-key endpoint. Exa adds another $7 of credits to the same API key.

References

Last modified on August 3, 2026