Scope fence – read before use The gen_ai semantic-convention namespace (open-telemetry/semantic-conventions-genai) has zero tagged releases – there is no version to pin against upstream, because upstream has not cut one. This tool pins its own attribute snapshot (below), stamps semconv_snapshot into every trace and receipt it emits, and expects that snapshot to drift as the upstream spec moves. A conformance result is a statement about one dated snapshot, not about a released standard. Zero network export – this page never opens an OTLP connection. Composed and linted traces stay in the browser; use the download button to save a file, then hand it to your own collector. This is a structural + attribute-presence linter, not a semantic validator of span timing correctness against your actual system, and not a KERI-grade trust check of any kind.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

Step 1 · Compose a Trace (gen_ai preset)

invoke_agent span with chat + execute_tool children · pinned gen_ai.* attribute set

gen_ai.system

gen_ai.agent.name

gen_ai.request.model

gen_ai.usage.input_tokens

gen_ai.usage.output_tokens

Include execute_tool child span

gen_ai.tool.name

Resource service.name

Step 2 · Import / Paste OTLP JSON to Lint

Structural validation + gen_ai attribute conformance · pinned snapshot below

OTLP/JSON trace

OTLP GenAI Span Composer & Semconv Linter