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

# Models

# `equabot models`

Model discovery, scanning, and configuration (default model, fallbacks, auth profiles).

Related:

* Providers + models: [Models](/providers/models)
* Provider auth setup: [Getting started](/start/getting-started)

## Common commands

```bash theme={null}
equabot models status
equabot models list
equabot models set <model-or-alias>
equabot models scan
```

`equabot models status` shows the resolved default/fallbacks plus an auth overview.
When provider usage snapshots are available, the OAuth/token status section includes
provider usage headers.
Add `--probe` to run live auth probes against each configured provider profile.
Probes are real requests (may consume tokens and trigger rate limits).

Notes:

* `models set <model-or-alias>` accepts `provider/model` or an alias.
* Model refs are parsed by splitting on the **first** `/`. If the model ID includes `/` (OpenRouter-style), include the provider prefix (example: `openrouter/moonshotai/kimi-k2`).
* If you omit the provider, Equabot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).

### `models status`

Options:

* `--json`
* `--plain`
* `--check` (exit 1=expired/missing, 2=expiring)
* `--probe` (live probe of configured auth profiles)
* `--probe-provider <name>` (probe one provider)
* `--probe-profile <id>` (repeat or comma-separated profile ids)
* `--probe-timeout <ms>`
* `--probe-concurrency <n>`
* `--probe-max-tokens <n>`

## Aliases + fallbacks

```bash theme={null}
equabot models aliases list
equabot models fallbacks list
```

## Auth profiles

```bash theme={null}
equabot models auth add
equabot models auth login --provider <id>
equabot models auth setup-token
equabot models auth paste-token
```

`models auth login` runs a provider plugin’s auth flow (OAuth/API key). Use
`equabot plugins list` to see which providers are installed.

Notes:

* `setup-token` runs `claude setup-token` on the current machine (requires the Claude Code CLI).
* `paste-token` accepts a token string generated elsewhere.