ContextQMD
Back to Openclaw

Chutes

docs/providers/chutes.md

2026.5.54.9 KB
Original Source

Chutes exposes open-source model catalogs through an OpenAI-compatible API. OpenClaw supports both browser OAuth and direct API-key auth for the bundled chutes provider.

PropertyValue
Providerchutes
APIOpenAI-compatible
Base URLhttps://llm.chutes.ai/v1
AuthOAuth or API key (see below)

Getting started

<Tabs> <Tab title="OAuth"> <Steps> <Step title="Run the OAuth onboarding flow"> ```bash openclaw onboard --auth-choice chutes ``` OpenClaw launches the browser flow locally, or shows a URL + redirect-paste flow on remote/headless hosts. OAuth tokens auto-refresh through OpenClaw auth profiles. </Step> <Step title="Verify the default model"> After onboarding, the default model is set to `chutes/zai-org/GLM-4.7-TEE` and the bundled Chutes catalog is registered. </Step> </Steps> </Tab> <Tab title="API key"> <Steps> <Step title="Get an API key"> Create a key at [chutes.ai/settings/api-keys](https://chutes.ai/settings/api-keys). </Step> <Step title="Run the API key onboarding flow"> ```bash openclaw onboard --auth-choice chutes-api-key ``` </Step> <Step title="Verify the default model"> After onboarding, the default model is set to `chutes/zai-org/GLM-4.7-TEE` and the bundled Chutes catalog is registered. </Step> </Steps> </Tab> </Tabs> <Note> Both auth paths register the bundled Chutes catalog and set the default model to `chutes/zai-org/GLM-4.7-TEE`. Runtime environment variables: `CHUTES_API_KEY`, `CHUTES_OAUTH_TOKEN`. </Note>

Discovery behavior

When Chutes auth is available, OpenClaw queries the Chutes catalog with that credential and uses the discovered models. If discovery fails, OpenClaw falls back to a bundled static catalog so onboarding and startup still work.

Default aliases

OpenClaw registers three convenience aliases for the bundled Chutes catalog:

AliasTarget model
chutes-fastchutes/zai-org/GLM-4.7-FP8
chutes-prochutes/deepseek-ai/DeepSeek-V3.2-TEE
chutes-visionchutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506

Built-in starter catalog

The bundled fallback catalog includes current Chutes refs:

Model ref
chutes/zai-org/GLM-4.7-TEE
chutes/zai-org/GLM-5-TEE
chutes/deepseek-ai/DeepSeek-V3.2-TEE
chutes/deepseek-ai/DeepSeek-R1-0528-TEE
chutes/moonshotai/Kimi-K2.5-TEE
chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506
chutes/Qwen/Qwen3-Coder-Next-TEE
chutes/openai/gpt-oss-120b-TEE

Config example

json5
{
  agents: {
    defaults: {
      model: { primary: "chutes/zai-org/GLM-4.7-TEE" },
      models: {
        "chutes/zai-org/GLM-4.7-TEE": { alias: "Chutes GLM 4.7" },
        "chutes/deepseek-ai/DeepSeek-V3.2-TEE": { alias: "Chutes DeepSeek V3.2" },
      },
    },
  },
}
<AccordionGroup> <Accordion title="OAuth overrides"> You can customize the OAuth flow with optional environment variables: 
| Variable | Purpose |
| -------- | ------- |
| `CHUTES_CLIENT_ID` | Custom OAuth client ID |
| `CHUTES_CLIENT_SECRET` | Custom OAuth client secret |
| `CHUTES_OAUTH_REDIRECT_URI` | Custom redirect URI |
| `CHUTES_OAUTH_SCOPES` | Custom OAuth scopes |

See the [Chutes OAuth docs](https://chutes.ai/docs/sign-in-with-chutes/overview)
for redirect-app requirements and help.
</Accordion> <Accordion title="Notes"> - API-key and OAuth discovery both use the same `chutes` provider id. - Chutes models are registered as `chutes/<model-id>`. - If discovery fails at startup, the bundled static catalog is used automatically. </Accordion> </AccordionGroup> <CardGroup cols={2}> <Card title="Model selection" href="/concepts/model-providers" icon="layers"> Provider rules, model refs, and failover behavior. </Card> <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear"> Full config schema including provider settings. </Card> <Card title="Chutes" href="https://chutes.ai" icon="arrow-up-right-from-square"> Chutes dashboard and API docs. </Card> <Card title="Chutes API keys" href="https://chutes.ai/settings/api-keys" icon="key"> Create and manage Chutes API keys. </Card> </CardGroup>