> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aireserve.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Roo Code

> Connect Roo Code's VS Code agent to the AI Reserve gateway with the OpenAI Compatible provider.

<Card title="Create your API key →" icon="key" href="https://portal.aireserve.com/profile#api-keys" horizontal>
  Mint an `aireserve_api_…` key in the portal — every Roo Code request is then
  metered and billed through your organization.
</Card>

Roo Code configures providers per profile inside VS Code
([Roo's OpenAI-compatible guide](https://docs.roocode.com/providers/openai-compatible)).
Open **Roo Code → Settings (gear icon) → Providers** and set:

| Field        | Value                                 |
| ------------ | ------------------------------------- |
| API Provider | `OpenAI Compatible`                   |
| Base URL     | `https://api.aireserve.com/v1`        |
| API Key      | your `aireserve_api_…` key            |
| Model        | `gpt-5.4-mini` (or any gateway model) |

Claude models work through the same OpenAI Compatible entry
(`claude-sonnet-4-6` as the model id) — the gateway bridges them. If you
prefer Roo's native **Anthropic** provider instead, enable its custom base
URL option and use the **host root** `https://api.aireserve.com` (no `/v1`;
Roo appends `/v1/messages` itself).

<Note>
  **Streaming usage chunks are served.** Roo Code requests
  `stream_options: {"include_usage": true}` and reads the final usage chunk
  to price each request in its context bar. The gateway returns that chunk on
  streamed completions, so Roo's token and cost tracking work as they do
  against first-party endpoints.
</Note>

## Verify

Start any task in Roo Code (for example, "explain this file") and watch it
stream. The request appears on your
[usage page](https://portal.aireserve.com/profile) seconds later — metered
against the key in the profile you just configured.