Skip to main content
Exa is a web search API built for AI agents, billed by operation type, such as deep search, fast search, or page contents. CostGraph reads Exa as FOCUS 1.2 records at a grain of one record per API key per price type per day.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call Exa once a day. Nothing to run.

You push it

You send us FOCUS records over the API. Credentials never leave your infrastructure.

​
Before you begin

  • Ask Exa support at [email protected] to enable team management for your team. Service keys are not available until they do.
  • In the Exa dashboard, open Service keys and create a service key. Copy it when Exa shows it after creation.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Exa.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Exa needs and marks the optional ones.
  4. Select Connect.
CostGraph verifies the credentials with a short fetch before saving, so a wrong value or a missing permission fails while you are still on the form.
Use an Exa service key, not the API key used to run searches; only a service key can read spend. Credentials are encrypted at rest and used only to read billing data. Revoke them in Exa at any time and the connection stops; nothing else is affected.

​
Push it yourself

Send the charges to CostGraph as FOCUS records instead. Push FOCUS data covers the connection id, the focus:write key, and the request shape.

​
Run the exporter

Rather than build that request yourself, run our exporter. It reads Exa on a schedule and pushes the records for you, wherever you want to run it: a container, a Kubernetes CronJob, or a binary on a machine you already have.
Your Exa credential stays where you put it, and only the finished FOCUS records reach CostGraph. Run the exporter covers the three ways to run it and the variables it reads.

​
What CostGraph does with it

Records land as raw billing rows, are normalised into line items, and roll up into daily cost. From there Exa spend appears in Cost Overview and in anomaly detection alongside every other provider. Spend is split per API key and operation type, so you can see which keys and which searches drive the bill.