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

> ## Agent Instructions
> Phaseo Gateway base URL: https://api.phaseo.app/v1. Send `Authorization: Bearer $PHASEO_API_KEY` with every request.
> Model IDs look like `provider/model`, for example `openai/gpt-6-astra`. Do not guess IDs: list them with `GET /v1/models` or check https://phaseo.app/models. `phaseo/free` routes to an available free model and needs no wallet balance.
> For new text integrations prefer `POST /v1/responses`. `POST /v1/chat/completions` (OpenAI format) and `POST /v1/messages` (Anthropic format) suit existing code.
> The full API contract is https://phaseo.app/docs/openapi/v1/openapi.yaml. Official SDKs: `@phaseo/sdk` (TypeScript) and `phaseo` (Python), plus Go, C#, PHP, Ruby and Rust.
> Search these docs over MCP at https://phaseo.app/docs/mcp, and install Phaseo skills with `npx skills add https://phaseo.app/docs`. If a page is wrong or out of date, report it with the MCP `submit_feedback` tool.
> Manage Phaseo accounts with the `phaseo` CLI (`npm install -g @phaseo/cli`, then `phaseo login` or `phaseo login --device-code`), the `/v1` Management API or the MCP server at `https://mcp.phaseo.app/mcp?access=manage`. Do not send users to the dashboard for account tasks. A person is still needed for sign-up, approving a sign-in, paying the first top-up on the checkout link that `phaseo credits add` returns when no card is saved, confirming each saved-card top-up from the emailed link, and account security (password, MFA, passkeys). Create API keys with `phaseo keys create --name <name> --json`; never guess one. Credit top-ups need `phaseo login --scopes billing:write` first. Task map: https://phaseo.app/docs/v1/developers/manage-from-an-agent.md.

# Roo Code

> Connect Roo Code to Phaseo through an OpenAI-compatible profile.

Use the Phaseo CLI to create a dedicated key, then configure Roo Code's provider profile manually. Roo Code keeps credentials in VS Code secret storage, so the final entry happens in the extension UI.

## Set up with the Phaseo CLI

```bash theme={null}
phaseo login
phaseo roo-code --model anthropic/claude-sonnet-4.6
```

## Configure Roo Code manually

1. Open Roo Code in VS Code.
2. Open **Settings**, then **Providers**.
3. Create a provider configuration profile and choose **OpenAI Compatible**.
4. Enter these values:

| Roo Code field | Value |
| - | - |
| Base URL | `https://api.phaseo.app/v1` |
| API Key | Output of `phaseo integrations credential roo-code` |
| Model | `anthropic/claude-sonnet-4.6` or the model printed by setup |

5. Save the profile and make it active.

Field labels can vary slightly between releases, but the profile needs the endpoint, key, and exact model ID.

## Verify

Ask Roo Code to reply with `PHASEO_ROO_OK`, then confirm the request appears in Phaseo activity.

## Remove

Delete the Phaseo profile or switch profiles, then run:

```bash theme={null}
phaseo integrations remove roo-code
```

The CLI cannot delete values in VS Code's private extension storage, but removal revokes the key.

## Troubleshooting

### Authentication fails

Retrieve the key again with `phaseo integrations credential roo-code`. Ensure the Base URL ends in `/v1`.

### Roo Code cannot find the model

Enter the exact Phaseo model ID manually, including its provider prefix.

### Chat works but tools fail

Switch to a model with tool-calling support.

## Related

* [Roo Code model providers](https://docs.roocode.com/providers/)
* [Coding Agents](https://phaseo.app/docs/v1/guides/integrations/coding-assistants.md)
* [Models](https://phaseo.app/docs/v1/api-reference/endpoint/models.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.