> 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/connecting-providers.md).

# Connecting Providers

While the Revenium SDK intercepts your live application traffic, connecting your underlying AI provider accounts unlocks the other half of the FinOps picture. Two kinds of account are linked on this screen: model providers such as OpenAI and Anthropic, and the organization-wide coding assistants **Cursor** and **GitHub Copilot**, whose usage Revenium pulls from the vendor's own API.

> **🔑 Note on Provider Permissions:** Different AI platforms have different permission models. Always check the specific instructions on the "Link Provider" screen to ensure you use the correct key type. Cursor needs a **team** API key rather than a personal one, and GitHub Copilot needs a token owned by an **organization owner** plus your organization slug.

When you add your provider API Keys, Revenium actively syncs with the provider to pull your granular usage records and workspace data. This immediately unlocks three key dashboards:

<table><thead><tr><th width="204.390625">Insight</th><th>What It Tells You</th></tr></thead><tbody><tr><td><strong>Providers</strong></td><td>The exact percentage of your provider bill that is actively metered and protected by Revenium.</td></tr><tr><td><strong>Models</strong></td><td>The true Cost per 1M tokens across all your active AI models so you can compare performance vs. price.</td></tr><tr><td><strong>API Keys</strong></td><td>A breakdown of cost, usage, and tokens by individual API key to help you spot rogue or uninstrumented scripts.</td></tr></tbody></table>

***

### <i class="fa-link">:link:</i> How to Link a Provider

1. Head over to [Connections > Providers](https://app.revenium.ai/connections/providers) in your left sidebar and click **+ Link Provider**.
2. Select your AI platform, provide its credentials, and hit **Create**. Most providers need only an API key; Cursor needs a team API key, and GitHub Copilot needs a token plus your organization slug.
   1. For details on how to connect Revenium's supported providers, [read here](/integrations/provider-integrations.md#how-to-link-a-provider).

Revenium authenticates the credential immediately and starts syncing your historical data. Refresh cadence varies by provider: Cursor syncs every 5 minutes, GitHub Copilot once daily.

***

### <i class="fa-eyes">:eyes:</i> Viewing Your Data

Once your key is authenticated, you don't have to wait for an end-of-month report. Head straight over to the **Overview** section in your left sidebar to see your data instantly populated across three main tabs:

* **Providers:** Check your Coverage — Metered as a share of Invoiced — and your total top-level spend.
* **Models:** View your Model Efficiency and compare your actual cost per 1M tokens.
* **API Keys:** Audit individual key usage to easily spot uninstrumented or rogue scripts.

> **Note on Syncing:** If you have a massive historical footprint, it may take a few moments for all data to appear. You can click **View Sync Logs** on the Provider dashboard to verify that Revenium is actively processing your records.


---

# 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/connecting-providers.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.