API Data Sources & OTLP

Use this page when your application already emits OpenTelemetry and you want to send that telemetry to Revenium. If you need runtime cost controls, richer business attribution, or the simplest first integration, start with the SDK path instead.

Quick Path

1. Create or choose a metering-only Revenium API key (rev_mk_) for the environment.
2. Point your OpenTelemetry exporter at Revenium.
3. Run a test request.
4. Confirm tokens, model, provider, and cost appear in logs, traces, or AI analytics.

export OTEL_EXPORTER_OTLP_ENDPOINT=https://api.revenium.ai/meter/v2/otlp
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer rev_mk_your_tenant_yourkey"
export OTEL_METRICS_EXPORTER=none

Revenium meters from traces and logs and answers the metrics endpoint with 410 Gone, so the metrics exporter is turned off here. To keep sending metrics to another backend, use the per-signal variables in OTLP Integration.

Python OpenTelemetry SDKs require the header value to be percent-encoded. Use Authorization=Bearer%20rev_mk_your_tenant_yourkey if your Python telemetry does not arrive.

When To Use This Path

Scenario	Start here
Your app already emits OpenTelemetry and you want telemetry ingestion	OTLP Integration
You need runtime cost controls, SDK attribution, or middleware setup	SDK Setup
You need to understand data-source identifiers	API Data Sources
You need schema-level API detail	API Reference

What Revenium Reads

For OTLP spans and logs, Revenium reads standard GenAI semantic convention fields for provider, model, token usage, timing, and errors. Revenium-specific attributes such as revenium.product.name, revenium.organization.name, and revenium.subscriber.id add business attribution.

For the full endpoint matrix, authentication priority, gRPC caveats, and payload examples, continue to OTLP Integration.