For the complete documentation index, see llms.txt. This page is also available as Markdown.

Quickstart

The fastest way to see Revenium working is to connect an AI coding assistant and your code repository. In under 10 minutes you have the assistant connected and live dashboards showing who is using each assistant and what it costs; once your code host is connected and its first sync completes, Revenium adds per-developer productivity metrics that line spend up against shipped pull requests.

Start with the walkthrough below, then add the other sources that matter to you.

You do not have to connect everything before the product is useful. Until data arrives, a dashboard tells you which source it needs and how to connect it, rather than showing an empty chart, and many views show a preview built from sample data so you can see the shape of the answer before you have your own. Previews are marked Sample Data wherever they appear, and each one is replaced by your own figures as soon as the source behind it starts reporting.

Start here: connect your coding assistant and GitHub

  • Connect Your Coding Assistant & Code Repository — connect Claude Code, Cursor, Codex, Copilot, or Gemini CLI, connect GitHub or GitLab, and see dashboards and per-developer productivity metrics in under 10 minutes.

  • Connect Your Agent — choose the setup path that matches how your coding agent runs.

Instrument your own code or API traffic

If you are metering an application you build rather than an off-the-shelf assistant, use one of these paths instead:

  • Connecting Providers — route provider traffic (OpenAI, Anthropic, and others) through Revenium.

  • API Data Sources & OTLP — send usage from your own services over OpenTelemetry.

  • Workspace Connections — link a workspace to organize sources and teams.

  • Examples — end-to-end walkthroughs for sales, coding, and customer-support agents.

Last updated

Was this helpful?