---
title: Send Fireworks AI traffic to Agent Analytics
description: "Two ways to capture Fireworks AI model traffic in Agent Analytics: wrap the OpenAI-compatible client with the AI SDK, or send Fireworks-managed OTLP traces to Amplitude."
product: general
lang: en
token_estimate: 331
---
# Send Fireworks AI traffic to Agent Analytics

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Fireworks AI traffic can reach Agent Analytics two ways: through the AI SDK wrapping Fireworks' OpenAI-compatible client, or through OTLP traces that Fireworks exports. Both produce the same `[Agent]` events.

## AI SDK wrap

Point the OpenAI-compatible client at `https://api.fireworks.ai/inference/v1` and wrap it with Python `amplitude-ai` or Node `@amplitude/ai`. Refer to [Instrument your agent with the AI SDK](https://amplitude.com/docs/amplitude-ai/agent-analytics/instrument-ai-sdk).

- The SDK captures the Router request ID as `[Agent] Provider Request ID`.
- The SDK doesn't send Fireworks' `x-multi-turn-session-id` header automatically.

## Fireworks-managed OTLP

When Fireworks exports traces, send them to the US or EU OTLP endpoint with your Amplitude project API key. Refer to [Configure your exporter](https://amplitude.com/docs/amplitude-ai/agent-analytics/instrument-opentelemetry#configure-your-exporter). Amplitude doesn't require an enablement request.

Fireworks must persist these values through every Router route:

- `user`
- A conversation or session ID
- `gen_ai.response.id`