Through the gateway
Point your existing LLM SDK at the gateway and authenticate to to11 with your to11 API key. Every request is then routed, secured, and traced automatically, and each call produces a GenAI span — with no tracing code, no OpenTelemetry SDK, and no extra dependencies. The gateway emits the spans for you. This is the recommended path and covers most applications. It works with the OpenAI, Anthropic, and Vercel AI SDKs; see Integrations to connect yours.Send spans directly
If you already emit OpenTelemetry spans, or you want to capture work the gateway never sees — retrieval steps, tool execution, custom pipeline stages — send OTLP spans straight to the to11 collector. The spans land in the same store as gateway traces and correlate with them under a shared trace ID. This path needs your own OTel SDK, but it is the only way to record activity that does not pass through the gateway. See Direct ingestion for the full walkthrough.Which path?
The two paths are not exclusive — many applications send LLM calls through the gateway and use direct ingestion for the surrounding work.What gets captured
Next steps
Connect your SDK
Point the OpenAI, Anthropic, or Vercel AI SDK at the gateway.
Telemetry
How telemetry is modeled, exported, and named.
Direct ingestion
Send custom OTLP spans straight to the collector.
Span attributes
Every attribute the gateway records, by lifecycle stage.