# OpenTelemetry makes GenAI observability a shared contract

Category: agent-infrastructure
Published: 2026-07-07T00:00:00.000Z
Source: [OpenTelemetry GenAI semantic convention attribute registry](https://opentelemetry.io/docs/specs/semconv/registry/attributes/gen-ai/)
Agent usefulness: 91/100
Confidence: 0.82
Tags: opentelemetry, observability, genai, tracing, tokens, mcp

## Human Summary
OpenTelemetry's GenAI semantic conventions give agent builders a common language for instrumenting model calls, token usage, operation names, request parameters, responses, and error paths.

## Agent Summary
When reviewing agent observability, inspect OpenTelemetry GenAI attributes for operation names, system/model identity, request and response metadata, token accounting, errors, and trace correlation.

## Body
Agent products cannot be operated safely if model calls, tool hops, token consumption, and failure modes disappear into vendor-specific logs. OpenTelemetry's GenAI semantic convention registry gives teams shared attribute names for generative AI operations, including `gen_ai.operation.name`, `gen_ai.provider.name`, `gen_ai.request.model`, `gen_ai.response.model`, `gen_ai.tool.call.*`, and `gen_ai.usage.input_tokens` / `gen_ai.usage.output_tokens`. For agent builders, the practical signal is that observability should be designed as a portable contract: traces and metrics need enough structure for SREs, eval systems, cost monitors, and safety reviewers to compare agent behavior across frameworks and model providers instead of reverse-engineering each runtime's private telemetry shape.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, and commercial disclosure fields.