Skip to main content
Getting your first trace into Veritrix takes about ten seconds of actual coding. You install one package, call one function, and every LLM call, tool execution, and agent handoff in your pipeline starts flowing into the dashboard automatically. This guide walks you through the full setup from account creation to your first live trace.
1

Create your free account

Go to app.veritrix.xyz and sign up. The Free tier gives you one project, 10,000 traced events per month, and 7-day retention — no credit card required.
If you’re setting up Veritrix for a team, start with the 14-day Team trial so you can explore alerting and multi-seat access from day one.
Once you’re logged in, create a new project and copy your API key from the project settings page.
2

Install the SDK

Install the Veritrix SDK into your Python environment.
Veritrix requires Python 3.8 or later. It works with all major agent frameworks out of the box — no additional adapters needed.
3

Initialize tracing in your agent

Add two lines at the entry point of your agent — before any LLM calls are made. Pass your project name to trace.init so spans are grouped correctly in the dashboard.
If you want to pass your API key explicitly (for example, in a CI environment), use the api_key parameter:
You can also set your API key via the VERITRIX_API_KEY environment variable and omit the api_key argument entirely — the SDK picks it up automatically.
4

Run your agent

Run your agent exactly as you normally would. Veritrix instruments in the background — there’s nothing else to change.
5

View your traces in the dashboard

Open app.veritrix.xyz and navigate to your project. You’ll see a live trace waterfall showing every span from your agent run.Each trace entry shows:
  • Span name — the operation that ran (e.g. planner.plan, researcher.search_docs)
  • Duration — how long the span took in milliseconds
  • Token counts — input and output tokens consumed
  • Statusok, fail, or retry
  • Payload — the full input and output for inspection
Here’s an example of what a completed trace looks like in the API and dashboard:
When a span fails, Veritrix generates a plain-language root-cause summary — for example:
Reviewer failed to parse Coder’s output as JSON on all 3 retries. The Coder’s tool schema expects diff: string, but it returned diff: object.
Click any span in the waterfall to inspect its full payload — the exact prompt sent to the model, the raw tool input and output, and any error details.

Next steps

Now that you have tracing running, explore the rest of the platform:

How It Works

Understand the three-phase Instrument → Trace → Diagnose model and what Veritrix captures automatically.

Integrations

Set up framework-specific instrumentation for OpenAI Agents SDK, LangGraph, CrewAI, AutoGen, and more.