Skip to main content

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.

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.

Choose a setup path

Installing with AI is the quickest. Use the manual flow if you want to review each change yourself.
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.
1

Install the CLI and authenticate

Install the Inference CLI globally and log in. Your browser will open to authenticate.
npm install -g @inference/cli && inf auth login
2

Run tracing instrumentation in your project

From your project root, run instrumentation in tracing mode.
cd /path/to/your/project && inf instrument --mode tracing
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.
Pick both instead of tracing if you also want to route requests through the Catalyst Gateway in the same pass.
3

Run your app

Run your application how you normally would. Traces stream to Catalyst as your code executes.
4

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.
That’s it. Spans are streaming to Catalyst and your trace is ready to inspect.

What gets captured

Span dataExamples
Inputs and outputsinput.value, output.value
Messagesuser, system, assistant, tool, and tool-result messages
Tool callstool names, IDs, JSON arguments, and tool results
Model metadatamodel name, provider/system, invocation parameters
Usageprompt, completion, total, and prompt-cache token counts
Agent structureagent spans, framework spans, tool spans, graph/node spans
Errorsexception 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.