# 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.

```bash
export OTEL_EXPORTER_OTLP_ENDPOINT=https://api.revenium.ai/v2/otlp
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer rev_mk_your_tenant_yourkey"
```

{% hint style="warning" %}
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.
{% endhint %}

## When To Use This Path

| Scenario                                                              | Start here                                            |
| --------------------------------------------------------------------- | ----------------------------------------------------- |
| Your app already emits OpenTelemetry and you want telemetry ingestion | [OTLP Integration](/integrations/otlp-integration.md) |
| You need runtime cost controls, SDK attribution, or middleware setup  | [SDK Setup](/integrations/sdk-setup.md)               |
| You need to understand data-source identifiers                        | [API Data Sources](/integrations/api-data-sources.md) |
| You need schema-level API detail                                      | [API Reference](https://revenium.readme.io)           |

## 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](/integrations/otlp-integration.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.revenium.io/get-started/quickstart/api-data-sources-and-otlp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.