> ## 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.

# Create A Router

> Create an endpoint that routes across your enabled models.

The default `/v1` router works without setup. Create another router when you need a different public model set, organization-registered custom models, provider keys, routing rules, or evals. You can set any router as the default for `/v1`. Each router has a stable `rtr_...` ID.

## Dashboard

Open **Routers** in the [Dari dashboard](https://app.dari.dev) and select **Create Router**. Choose:

* The models the router may use.
* **Dari-managed** or **BYOK** keys for their providers.
* **SLM (Small Language Model) Router**, which uses a small selector model for automatic selection, or **Describe Your Router**, which asks the selector to apply your natural-language rules.
* Whether to use [Speculative Routing](/router/speculative-routing) for lower-latency follow-up turns. It is enabled by default.

After creation, copy the endpoint from the router detail page:

```text theme={null}
https://routing.dari.dev/rtr_123/chat/completions
```

Public catalog models and organization-registered [custom models](/router/configure-models#custom-models) can be used together in the same router.

## YAML

You can also create a router from a local manifest with the public Dari CLI. Install it on macOS or Linux:

```bash theme={null}
curl -fsSL https://raw.githubusercontent.com/mupt-ai/dari-cli/main/install.sh | bash
```

Then create a manifest:

```yaml theme={null}
name: Production Router
enabled_models:
  - openai/gpt-5.6-sol
  - anthropic/claude-sonnet-4-6
provider_key_sources:
  openai: managed
  anthropic: managed
routing_strategy: slm
```

```bash theme={null}
dari auth login
dari router create ./router.yml
```

`slm` is automatic routing. Use `provider_key_envs` to read BYOK values from environment variables instead of storing secrets in YAML.

The YAML command uses the platform default and enables speculative routing. Use the dashboard when you need to switch it off; the current public CLI manifest does not expose that setting.

See [Speculative Routing](/router/speculative-routing), [Configure Models](/router/configure-models), [Configure Provider Keys](/router/configure-provider-keys), and [Router Evals](/evals/overview) for optional settings.