Point your OpenTelemetry exporter at SuperOrgs

Most teams that run agents in production already have traces. OpenTelemetry is how their engineers see what a request did, and the libraries their agents are built on, the AI SDK, OpenLLMetry, OpenInference, already emit spans for model calls and tool calls. Until now none of that reached SuperOrgs unless someone added the SDK or wrote to the HTTP contract.

Now it does. Point your trace exporter at SuperOrgs with your agent's credential, and its runs appear on the agent's activity page with their tool calls and token usage. No SDK.

What shipped

An OTLP trace receiver. SuperOrgs accepts OpenTelemetry traces over HTTP, as protobuf or JSON, gzipped or not. Four exporter settings, or one exporter block in an OpenTelemetry Collector, and the agent is reporting.

The same credential. The credential you mint for an agent on the Connectors page works for OpenTelemetry too. The organization and the agent come only from that credential, never from anything in the trace.

A trace becomes a run. GenAI steps become the run's timeline, drawn as a waterfall in tree order. Model calls become token usage, priced server-side where SuperOrgs has a rate for the model. Tool executions become tool calls and their results. The OpenTelemetry GenAI conventions are read, along with OpenLLMetry, the AI SDK's telemetry, and OpenInference model calls.

Nothing you would not want stored. Prompts, responses, tool payloads, and error text are discarded on receipt and never stored. If content must not leave your servers at all, turn off content capture in your instrumentation.

Built for real exporters. A resent batch is recognized as a duplicate. A trace whose root arrives late still ends its run correctly. Nested model calls are billed once. Oversized or malformed batches are refused with the status codes the OTLP specification expects, so an exporter never retries a poison batch forever.

One path per agent

Use the SDK or OpenTelemetry for an agent, not both. The connector page warns when one agent reports through both within a day. If the agent's traces already go to another backend, add a second exporter, or route a Collector pipeline that carries this agent's traces alone, because every span it forwards lands under this one agent.

Turning it on

1. Mint a credential for the agent on the Connectors page, under SuperOrgs SDK, or reuse the one it already has.
2. Set the four exporter variables where the agent runs, or add the exporter block to your Collector. Both are on the connector page and in the docs.
3. Run the agent. Its next trace shows up on its activity page, labeled OpenTelemetry.

If you already use SuperOrgs, this is a five-minute change to an environment file. If you do not, get a demo.