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:
Add metering to application code
Meter + backfill AI Assistants such as Claude Code, Cowork, Gemini, Codex, etc
Connect OpenAI, Anthropic, Cursor, GitHub Copilot, or other provider billing accounts
Send standard OpenTelemetry data
Send custom payloads directly to Revenium
Let an AI coding assistant read Revenium docs while you integrate
Let an AI agent query or operate Revenium through tools
Use Revenium from the command line
Revvy CLI + use Revenium CLI for AI assistant onboarding
Connect team workflow systems
The canonical API domain for examples in this documentation is https://api.revenium.ai.
What Lives Here
Please see AI Assistantssection for AI assitant integrations
Python, Node.js, Go, LangChain, n8n, and other middleware setup.
Choosing the right key type and understanding current scoped-key limits.
Connecting provider accounts for billing and historical usage import.
Understanding application data sources and integration identifiers.
OpenTelemetry endpoints, authentication, GenAI attributes, and examples.
Letting AI coding assistants retrieve Revenium docs and schemas.
Connecting MCP-compatible agents to Revenium.
Guided command-line setup and codebase instrumentation.
Route AI cost alerts, anomaly notifications, and reports to Slack channels.
Subscribing to insight run and recommendation feedback events instead of polling.
Trying direct API calls and reading schema-level details.
Need custom payloads or a non-SDK path?
Start with OTLP Integration or API Reference.
Last updated
Was this helpful?