> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/get-started/quickstart.md).

# 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](/get-started/quickstart/5-minute-quickstart.md): 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](/get-started/quickstart/connect-your-agent.md): 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. None of these puts a Revenium server between your application and the AI provider: your requests take the route they take today, and Revenium receives a record of the usage.

* [SDK Setup](/integrations/sdk-setup.md): add a Revenium SDK or middleware to your application so it reports each AI call as it happens.
* [Connecting Providers](/get-started/quickstart/connecting-providers.md): link your provider accounts, such as OpenAI and Anthropic, so Revenium pulls usage and billing records from each provider's own API.
* [API Data Sources & OTLP](/get-started/quickstart/api-data-sources-and-otlp.md): send usage from your own services over OpenTelemetry.
* [LiteLLM Proxy Setup](/integrations/litellm-proxy-setup.md): if you already run a LiteLLM proxy, register Revenium as a callback inside it.
* [Workspace Connections](/get-started/quickstart/workspace-connections.md): link a workspace to organize sources and teams.
* [Examples](/get-started/quickstart/examples.md): end-to-end walkthroughs for sales, coding, and customer-support agents.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revenium.io/get-started/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.