> ## Documentation Index
> Fetch the complete documentation index at: https://docs.costgraph.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Exa

> Bring Exa web search API cost into CostGraph, pulled by us or pushed by you

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

<CardGroup cols={2}>
  <Card title="CostGraph pulls it" icon="cloud-arrow-down">
    You supply read-only credentials and we call Exa once a day. Nothing to run.
  </Card>

  <Card title="You push it" icon="cloud-arrow-up">
    You send us FOCUS records over the API. Credentials never leave your infrastructure.
  </Card>
</CardGroup>

## Before you begin

* Ask Exa support at [support@exa.ai](mailto:support@exa.ai) 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.

<Note>
  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.
</Note>

## Push it yourself

Send the charges to CostGraph as FOCUS records instead. [Push FOCUS data](/costgraph/integrations/focus-push) 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.

```bash theme={null}
focus-exporter --provider exa --sink costgraph
```

Your Exa credential stays where you put it, and only the finished FOCUS records reach
CostGraph. [Run the exporter](/costgraph/integrations/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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.