Skip to main content
Record what each Exa search costs next to your LLM spend. Every search becomes a tool span with its query, results, latency and dollar cost, and the cost counts toward the trace total.
traceroot does not auto-instrument Exa. You trace the search with observe and report its cost yourself, and traceroot stores the cost you report. See Tool and API calls for how reported costs add up.

Install

Reporting a cost requires traceroot 0.5.0 or later, or @traceroot-ai/traceroot 0.7.0 or later.

Set up

Initialize traceroot once at startup. No integration flag is needed: the observe wrapper in the next step traces the search.

Usage

Exa returns the dollar cost of each request in costDollars. To record it:
  1. Wrap the search in a function traced as a tool span (type="tool").
  2. Read costDollars.total from the response.
  3. Report it with update_current_span(cost=...) (updateCurrentSpan in TypeScript) while that span is open.
Call web_search from your agent like any other function. Its span nests under the span that called it, and its cost adds to that trace’s total.
Span details for an exa_search tool span with a cost of 0.007000, its search query input and the search results output

The tool span carries the price the search API returned

Verify

Run your code and confirm the trace arrives:
  1. In the traceroot UI: Navigate to Tracing > Traces in traceroot Cloud. You should see an exa_search span, at the root or under your agent’s span. Open it to see its cost; the trace’s total cost includes it.
  2. Via the CLI: Run traceroot traces list to inspect your recent traces from the terminal.

What gets captured

Limitations

  • A response without costDollars records no cost on the span.

Next steps

Python SDK Reference

Explore the full Python SDK reference and instrumentation options.

Price in the response

Report the price a provider returns with each request