Billing dashboard
Add credits, configure auto recharge, and view invoices.
API keys
Review usage and set a lower limit for an individual key.
Pricing
Compare current rates across Exa products.
Plans at a glance
Contact Us
We’ll advise on the best set up to handle latency, scale, ZDR, and more.
Billing basics
Requests are charged against prepaid credits at the rates in Pricing or under your Enterprise contract. Team owners can add credits from the Billing dashboard; payments are processed through Stripe. If your team exhausts its credits, requests return402 Payment Required. An API key that reaches its assigned budget also returns 402. Add credits or ask a team administrator to adjust the key’s budget. See Error codes.
For historical usage by API key, use Get API key usage.
Rate limits
Rate limits are measured in queries per second (QPS) and apply to your team as a whole, across all of its API keys. You can give an individual key a lower limit from the API Keys page, but its traffic still counts toward the team limit.
Some endpoints share rate limit capacity. Limits are subject to change and can vary by plan; Websets searches also have plan-based concurrency limits, which you can check with Get Team Info.
When you exceed a limit, requests return
429 Too Many Requests. Wait for the Retry-After header when present, or retry with exponential backoff. See Error codes.
Agent limits
Agent limits are two separate controls: how many runs can be in progress at once, and how fast you can start new ones.- Concurrency: 50 Agent runs can be in progress at a time. This limit is separate from your QPS and does not change when your QPS is raised. Starting a run past the limit returns
429with error codeCONCURRENCY_LIMIT_REACHED; wait for a run to finish or contact us to raise your concurrency limit. - Starting runs:
POST /agent/runsdraws from your account QPS, and each run start counts as two requests. You can start runs at half your QPS, so an account with the default 10 QPS can start 5 runs per second, and 25 QPS allows 12 per second. - Polling:
GETrequests for run status, events, and run lists do not count against your QPS and never block dispatch, so poll running Agents independently of how fast you start new ones.
25 QPS on pay as you go
Add $1,000 in credits within any 30-day window and your team’s rate limit rises to 25 QPS for 90 days, automatically. The threshold counts credits you purchase, not credits you spend, and requalifying resets the 90 days. Track your progress on the Billing dashboard. Need more than 25 QPS? Talk to sales.Auto recharge
Auto recharge purchases credits when your balance reaches a threshold you choose. Configure it from the Billing dashboard.
For example, a $100 recharge amount, $10 threshold, and $500 monthly maximum purchases $100 whenever the balance reaches $10, up to $500 in automatic purchases during the cycle.
For an upcoming launch or other high-volume workload, add enough credits in advance and set an auto-recharge amount that avoids many small payment attempts.
Receipts and invoices
Exa emails receipts for credit purchases and auto recharges from billing@exa.ai. Add the address to your allow list if needed. Your full invoice history is available in the Billing dashboard. Postpaid invoice billing is available with an Enterprise plan.Get help
Increase your limits
Request more than 25 QPS, custom concurrency, volume pricing, or postpaid billing.
Billing support
Get help with payments, credits, invoices, or account billing questions.