Skip to main content
Veritrix integrates with CAMEL-AI’s communicative agent framework to give you full visibility into multi-agent role-playing conversations, task decomposition pipelines, and tool-augmented agents. After a single call to trace.init(), every message exchange between agents, every LLM call, and every tool invocation is captured as a structured trace — allowing you to analyze conversation quality, measure per-agent cost and latency, and debug complex multi-agent workflows without changing any of your agent definitions.

Prerequisites

  • Python 3.10 or higher
  • An active Veritrix account and API key
  • CAMEL-AI installed

Installation & Setup

1

Install Veritrix and CAMEL-AI

To include CAMEL-AI’s optional tool and model integrations, install the extras you need:
2

Initialize Veritrix tracing

Call trace.init() once at application startup, before you instantiate any agents or models.
3

Use CAMEL-AI agents as normal

Veritrix instruments the CAMEL-AI agent runtime automatically. Your role assignments, system messages, and conversation loops remain unchanged.

Example: Single ChatAgent

The following example creates a single CAMEL ChatAgent with a custom role and runs a one-turn conversation. Veritrix records the full LLM call, including the system prompt, user message, and model response.

Example: Role-Playing Multi-Agent Conversation

For CAMEL’s signature role-playing setup — where two agents collaborate toward a shared task — Veritrix traces every turn of the conversation and links each agent’s messages within the same trace.

What Gets Captured Automatically

Each agent in a role-playing session is represented as a distinct entity in Veritrix, so you can filter traces by role name and compare the behavior of individual agents across multiple runs.

OpenTelemetry Compatibility

Veritrix is built on OpenTelemetry, so every span it emits for your CAMEL-AI workflows is a fully compliant OTel span. You can export these spans to any OTel-compatible backend — whether you run Jaeger, Grafana Tempo, Honeycomb, or your own collector — without any additional setup.
To route Veritrix traces to a custom OTel exporter or integrate them with an existing observability stack, see the OpenTelemetry integration page.