Crew Studio launches with native Arize AX tracing and evaluation

CrewAI launched Crew Studio, an Automated Agent Builder with native Arize AX tracing and evaluation integration, enabling teams to send traces from the first run without custom instrumentation. The integration, built on OpenTelemetry standards, provides span-level visibility, cost breakdowns, and online evaluations to help teams inspect agent behavior and validate fixes before redeploying.

Co-Authored by Richard Young, Director, Partner Solutions Architecture & Jesse Miller, VP of Product, CrewAI. CrewAI has launched Crew Studio https://docs-platform.crewai.com/platform/en/features/crew-studio , the Automated Agent Builder. Through a native Arize AX https://arize.com/docs/ax/get-started/get-started-tracing integration, teams can send traces https://arize.com/glossary/trace/ from Studio to Arize from the first run without adding custom instrumentation code. Builders and platform teams can then inspect agent behavior, evaluate quality, identify failures, and test improvements before redeploying. What is Crew Studio Crew Studio is a new building layer for agentic systems. It is designed to bridge a familiar gap in enterprise agent development: visual tools can become limiting as workflows grow more complex, while code-first frameworks may be inaccessible to the domain experts closest to the underlying business process. Studio brings those workflows together across four stages: Discover. A discovery module helps teams identify which agent use cases are worth building, grounded in patterns from real deployments rather than guesswork. Build. Teams describe the system they want, and Studio turns that into a working architecture: agents, tasks, tools, models, flows, memory, and MCP https://arize.com/glossary/mcp-model-context-protocol/ connections. The output is informed by more than 700,000 patterns and architectures from billions of executions on the CrewAI platform. Own. You own what gets built. Download the code, modify it, extend it, and move from visual building to code without starting over. Run. Deploy to the same CrewAI AMP infrastructure your engineers already use, with governance, security, cost controls, and deployment paths attached. Business teams can build while platform teams can stay in control. Why observability has to be there from the start Studio will put agent building in the hands of many more people. That’s the point. But it also means more agents in production, built by people who may never open the underlying code. When one of those agents misbehaves, someone has to answer what happened, which step failed, what it cost, and whether the fix worked. That’s the gap this integration closes. Studio and AMP give teams traces, cost visibility, and governance in the same environment where agents are built and deployed. Arize AX https://arize.com/docs/ax/get-started/get-started-tracing adds a dedicated evaluation layer on top: online evals https://arize.com/resources/online-llm-evaluations/ against live traffic, labeling queues, ground truth datasets, and experiments https://arize.com/docs/ax/evaluate/run-evals-on-experiments to validate a fix before it ships. Traces from every Studio deployment can land in Arize, where teams get span-level visibility into each agent run, latency and token cost breakdowns, and agent graphs https://arize.com/docs/ax/observe/tracing-concepts/agent-graphs that show how the system actually behaves in production. Visibility is only the first step. Arize runs online evaluations https://arize.com/resources/online-llm-evaluations/ against live traffic, so quality issues surface as they happen instead of when a user complains. Flagged traces https://arize.com/glossary/trace/ route to labeling queues where human reviewers turn them into ground truth datasets. Those datasets feed experiments to test fixes before they ship. The resulting feedback loop is straightforward: trace, evaluate, label, improve, redeploy. Every production run adds evidence that makes the next version better. Built on OpenTelemetry standards This integration works because of a capability Arize announced recently: native support for the OpenTelemetry GenAI semantic conventions https://arize.com/docs/ax/concepts/otel-openinference/semantic-conventions , alongside OpenInference https://arize.com/docs/ax/concepts/otel-openinference/overview . Arize AX https://arize.com/docs/ax/get-started/get-started-tracing can ingest those traces directly and also supports applications instrumented with OpenInference https://arize.com/docs/ax/concepts/otel-openinference/overview semantic conventions. To connect the platforms, configure Studio with Arize’s OTLP endpoint and authentication headers. No custom tracing code is required. Because the integration uses open telemetry standards https://arize.com/docs/ax/concepts/otel-openinference/overview , teams retain flexibility across frameworks, models, and observability https://arize.com/glossary/agent-observability/ backends. How to connect Crew Studio to Arize AX Connecting Crew Studio to Arize AX requires only a few configuration steps. 1. In Arize AX, go to Settings → API Keys. Copy your Space ID and create or copy an API key. 2. In CrewAI, go to Settings → Organization → OpenTelemetry Collectors, click Add Collector, and select OpenTelemetry Traces.