Keys / Exa

EXA_API_KEY

The Exa API key your app searches the web and fetches page contents with. Each key belongs to a team.

Expires
the docs don't say
API
create, list, update, rotate and delete, with a service account key

Get it

Create one on dashboard.exa.ai/api-keys. The steps aren't recorded yet.

Set it

EXA_API_KEY=...

The Python (exa-py) and JavaScript (exa-js) SDKs read it from this variable when you don't pass a key. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. If your team has the Team Management API (Exa turns it on by request), rotate the key with a grace period of up to 90 days. The key keeps its name, rate limit and budget, and the old secret works until the grace period ends.
  2. Without it, create a new key in the dashboard with the same rate limit and budget.
  3. Deploy the new secret everywhere that reads EXA_API_KEY.
  4. Check that requests succeed, then revoke the previous secret, or delete the old key.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16