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

# Environment setup

> Configure base URLs, API keys, and local development values.

## Canonical domains

| Surface     | URL                             |
| ----------- | ------------------------------- |
| Web console | `https://meshrouter.app`        |
| API         | `https://api.meshrouter.app`    |
| Docs        | `https://meshrouter.app/docs`   |
| Status      | `https://status.meshrouter.app` |

## SDK values

```bash theme={null}
OPENAI_BASE_URL=https://api.meshrouter.app/v1
OPENAI_API_KEY=mesh_live_...
```

MESH-specific SDKs use `MESH_API_KEY` by convention:

```bash theme={null}
MESH_API_KEY=mesh_live_...
```

## Routing credentials

Routing credentials are configured at deploy time and never appear in client applications.
Application code only needs a `mesh_live_...` API key — pick a model from the
[MESH catalogue](/models) and call the API.

`/v1/providers/health` and `/v1/providers/config` are admin-only endpoints that return redacted,
non-secret routing data; they are not part of the per-request flow.