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

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

* [Connecting Providers](/get-started/quickstart/connecting-providers.md) — route provider traffic (OpenAI, Anthropic, and others) through Revenium.
* [API Data Sources & OTLP](/get-started/quickstart/api-data-sources-and-otlp.md) — send usage from your own services over OpenTelemetry.
* [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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.