Integration Options

Use this page to choose the right way to connect data, tools, and workflows to Revenium. The detailed setup lives in the child pages so this page stays scannable.

Choose an Integration Path

Start with the path that matches what you are connecting:

Goal	Best starting point
Add metering to application code	SDK Setup
Connect OpenAI, Anthropic, or other provider billing accounts	Provider Integrations
Send standard OpenTelemetry data	OTLP Integration
Send custom payloads directly to Revenium	API Reference
Let an AI coding assistant read Revenium docs while you integrate	Context7 and AI Docs Access
Let an AI agent query or operate Revenium through tools	MCP Server
Use Revenium from the command line	Revvy CLI
Connect team workflow systems	Slack

The canonical API domain for examples in this documentation is https://api.revenium.ai.

What Lives Here

Page	Use it for
SDK Setup	Python, Node.js, Go, LangChain, n8n, and other middleware setup.
API Key Permissions	Choosing the right key type and understanding current scoped-key limits.
Provider Integrations	Connecting provider accounts for billing and historical usage import.
API Data Sources	Understanding application data sources and integration identifiers.
OTLP Integration	OpenTelemetry endpoints, authentication, GenAI attributes, and examples.
Context7 and AI Docs Access	Letting AI coding assistants retrieve Revenium docs and schemas.
MCP Server	Connecting MCP-compatible agents to Revenium.
Revvy CLI	Guided command-line setup and codebase instrumentation.
Slack	Route AI cost alerts, anomaly notifications, and reports to Slack channels.
API Reference	Trying direct API calls and reading schema-level details.
Need custom payloads or a non-SDK path?	Start with OTLP Integration or API Reference.