# Connections (BYOK)

Already under contract with a provider? Connect that provider's API key and RouterGrowth routes calls to it through your key: your rates, your quota, and the calls are not metered by RouterGrowth. Some providers are BYOK-only (`requires_byok: true` in [inspect](/docs/api/inspect) offers).

Credentials are encrypted at rest and never returned by any endpoint.

## List connections

```text
GET /v1/connections
```

```json
{
  "items": [
    {
      "provider": "...",
      "status": "active",
      "last_verified_at": "2026-09-02T09:30:00+00:00",
      "created_at": "2026-09-01T12:00:00+00:00"
    }
  ]
}
```

## Connect a provider

```text
POST /v1/connections/{provider}
```

```json
{"api_key": "the provider's API key"}
```

Connecting an already-connected provider replaces the stored credential and reactivates the connection. Unknown provider slugs return `provider_not_available`.

## Disconnect

```text
DELETE /v1/connections/{provider}
```

Marks the connection revoked; routing stops considering that provider through your key immediately.

## How routing treats BYOK

A connected provider competes in [auto routing](/docs/api/run) like any other offer, and you can pin it with `routing.provider`. Inspect shows `connected: true` on its offer once the connection is active.