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

# Router API Overview

> Send routed model traffic over HTTP.

Send requests to `https://routing.dari.dev/v1` with a Routing API key and `model: "dari/routing"`. The `/v1` path uses your organization's default router, which starts with Dari's managed model set and requires no setup.

```bash theme={null}
curl https://routing.dari.dev/v1/chat/completions \
  -H "Authorization: Bearer $DARI_ROUTING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "dari/routing",
    "messages": [{"role": "user", "content": "Hello from Dari"}]
  }'
```

Address a specific router by its `rtr_...` ID instead of `/v1`. Both forms accept the same request bodies, and endpoint paths vary by protocol:

| Protocol           | Default Router         | Specific Router                 |
| ------------------ | ---------------------- | ------------------------------- |
| Chat Completions   | `/v1/chat/completions` | `/{router_id}/chat/completions` |
| Responses          | `/v1/responses`        | `/{router_id}/v1/responses`     |
| Anthropic Messages | `/v1/messages`         | `/{router_id}/v1/messages`      |

Claude Code, Codex, and Pi take base URLs and append their protocol-specific paths, so use the base URL shown in each coding-agent guide.

<CardGroup cols={2}>
  <Card title="Chat Completions API" icon="comment-dots" href="/api-reference/router/chat-completions">
    OpenAI-compatible Chat Completions.
  </Card>

  <Card title="Responses API" icon="comments" href="/api-reference/router/responses">
    OpenAI Responses over HTTP.
  </Card>
</CardGroup>