Catalyst Tracing captures the full execution of your AI apps and agents: LLM calls, tool calls, framework steps, and any custom spans you add. Drop the SDK into your app, point it at Catalyst, and traces start flowing. This guide gets you from zero to a captured trace. The example uses OpenAI because it is the smallest end-to-end setup. The same flow works for Anthropic, LangChain, LangGraph, the Vercel AI SDK, OpenAI Agents, LiveKit Agents, Pydantic AI, and the other supported integrations. To get started with Catalyst, create a free account at inference.net.Documentation Index
Fetch the complete documentation index at: https://docs.inference.net/llms.txt
Use this file to discover all available pages before exploring further.
Choose a setup path
Installing with AI is the quickest. Use the manual flow if you want to review each change yourself.- Install with AI
- Install manually
Use the Inference CLI to launch a coding agent like Claude Code to install the tracing SDK, configure export, and wire up your existing LLM clients.
Install the CLI and authenticate
Install the Inference CLI globally and log in. Your browser will open to authenticate.
Run tracing instrumentation in your project
From your project root, run instrumentation in tracing mode.The command guides you through the following workflow:
- Select a coding agent: Claude Code, OpenCode, or Codex.
- Scan your codebase for LLM clients and agent frameworks.
- Install the tracing SDK and configure export to Catalyst.
- Wire
setup()into your app entrypoint so spans start before clients are constructed. - Add stable service and agent identity so traces group cleanly in the dashboard.
- Review the generated changes before applying them.
Run your app
Run your application how you normally would. Traces stream to Catalyst as your code executes.
View your trace
Open the dashboard and filter by your service name to see the captured trace tree.
Want the full canonical guide for this workflow? See Install with AI.
What gets captured
| Span data | Examples |
|---|---|
| Inputs and outputs | input.value, output.value |
| Messages | user, system, assistant, tool, and tool-result messages |
| Tool calls | tool names, IDs, JSON arguments, and tool results |
| Model metadata | model name, provider/system, invocation parameters |
| Usage | prompt, completion, total, and prompt-cache token counts |
| Agent structure | agent spans, framework spans, tool spans, graph/node spans |
| Errors | exception status and error details on failed spans |
Next steps
Analyze your traces
Inspect trace trees in the dashboard and run Halo to find what to improve.
Add more integrations
Instrument Anthropic, LangChain, LangGraph, Vercel AI SDK, agent frameworks, and more.
Set agent identity
Add stable agent IDs so the Agents dashboard groups runs correctly.
Wrap custom work
Add spans around your own orchestration, retrieval, and routing code.