fengming 0.3.10 → 0.3.11

package/docs/providers/bedrock.md

@@ -1,414 +0,0 @@
----
-summary: "Use Amazon Bedrock (Converse API) models with FengMing"
-read_when:
-  - You want to use Amazon Bedrock models with FengMing
-  - You need AWS credential/region setup for model calls
-title: "Amazon Bedrock"
----
-
-FengMing can use **Amazon Bedrock** models via its **Bedrock Converse**
-streaming provider. Bedrock auth uses the **AWS SDK default credential chain**,
-not an API key.
-
-| Property | Value                                                       |
-| -------- | ----------------------------------------------------------- |
-| Provider | `amazon-bedrock`                                            |
-| API      | `bedrock-converse-stream`                                   |
-| Auth     | AWS credentials (env vars, shared config, or instance role) |
-| Region   | `AWS_REGION` or `AWS_DEFAULT_REGION` (default: `us-east-1`) |
-
-## Getting started
-
-Choose your preferred auth method and follow the setup steps.
-
-<Tabs>
-  <Tab title="Access keys / env vars">
-    **Best for:** developer machines, CI, or hosts where you manage AWS credentials directly.
-
-    <Steps>
-      <Step title="Set AWS credentials on the gateway host">
-        ```bash
-        export AWS_ACCESS_KEY_ID="EXAMPLE_AWS_ACCESS_KEY_ID"
-        export AWS_SECRET_ACCESS_KEY="..."
-        export AWS_REGION="us-east-1"
-        # Optional:
-        export AWS_SESSION_TOKEN="..."
-        export AWS_PROFILE="your-profile"
-        # Optional (Bedrock API key/bearer token):
-        export AWS_BEARER_TOKEN_BEDROCK="..."
-        ```
-      </Step>
-      <Step title="Add a Bedrock provider and model to your config">
-        No `apiKey` is required. Configure the provider with `auth: "aws-sdk"`:
-
-        ```json5
-        {
-          models: {
-            providers: {
-              "amazon-bedrock": {
-                baseUrl: "https://bedrock-runtime.us-east-1.amazonaws.com",
-                api: "bedrock-converse-stream",
-                auth: "aws-sdk",
-                models: [
-                  {
-                    id: "us.anthropic.claude-opus-4-6-v1:0",
-                    name: "Claude Opus 4.6 (Bedrock)",
-                    reasoning: true,
-                    input: ["text", "image"],
-                    cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                    contextWindow: 200000,
-                    maxTokens: 8192,
-                  },
-                ],
-              },
-            },
-          },
-          agents: {
-            defaults: {
-              model: { primary: "amazon-bedrock/us.anthropic.claude-opus-4-6-v1:0" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        fengming models list
-        ```
-      </Step>
-    </Steps>
-
-    <Tip>
-    With env-marker auth (`AWS_ACCESS_KEY_ID`, `AWS_PROFILE`, or `AWS_BEARER_TOKEN_BEDROCK`), FengMing auto-enables the implicit Bedrock provider for model discovery without extra config.
-    </Tip>
-
-  </Tab>
-
-  <Tab title="EC2 instance roles (IMDS)">
-    **Best for:** EC2 instances with an IAM role attached, using the instance metadata service for authentication.
-
-    <Steps>
-      <Step title="Enable discovery explicitly">
-        When using IMDS, FengMing cannot detect AWS auth from env markers alone, so you must opt in:
-
-        ```bash
-        fengming config set plugins.entries.amazon-bedrock.config.discovery.enabled true
-        fengming config set plugins.entries.amazon-bedrock.config.discovery.region us-east-1
-        ```
-      </Step>
-      <Step title="Optionally add an env marker for auto mode">
-        If you also want the env-marker auto-detection path to work (for example, for `fengming status` surfaces):
-
-        ```bash
-        export AWS_PROFILE=default
-        export AWS_REGION=us-east-1
-        ```
-
-        You do **not** need a fake API key.
-      </Step>
-      <Step title="Verify models are discovered">
-        ```bash
-        fengming models list
-        ```
-      </Step>
-    </Steps>
-
-    <Warning>
-    The IAM role attached to your EC2 instance must have the following permissions:
-
-    - `bedrock:InvokeModel`
-    - `bedrock:InvokeModelWithResponseStream`
-    - `bedrock:ListFoundationModels` (for automatic discovery)
-    - `bedrock:ListInferenceProfiles` (for inference profile discovery)
-
-    Or attach the managed policy `AmazonBedrockFullAccess`.
-    </Warning>
-
-    <Note>
-    You only need `AWS_PROFILE=default` if you specifically want an env marker for auto mode or status surfaces. The actual Bedrock runtime auth path uses the AWS SDK default chain, so IMDS instance-role auth works even without env markers.
-    </Note>
-
-  </Tab>
-</Tabs>
-
-## Automatic model discovery
-
-FengMing can automatically discover Bedrock models that support **streaming**
-and **text output**. Discovery uses `bedrock:ListFoundationModels` and
-`bedrock:ListInferenceProfiles`, and results are cached (default: 1 hour).
-
-How the implicit provider is enabled:
-
-- If `plugins.entries.amazon-bedrock.config.discovery.enabled` is `true`,
-  FengMing will try discovery even when no AWS env marker is present.
-- If `plugins.entries.amazon-bedrock.config.discovery.enabled` is unset,
-  FengMing only auto-adds the
-  implicit Bedrock provider when it sees one of these AWS auth markers:
-  `AWS_BEARER_TOKEN_BEDROCK`, `AWS_ACCESS_KEY_ID` +
-  `AWS_SECRET_ACCESS_KEY`, or `AWS_PROFILE`.
-- The actual Bedrock runtime auth path still uses the AWS SDK default chain, so
-  shared config, SSO, and IMDS instance-role auth can work even when discovery
-  needed `enabled: true` to opt in.
-
-<Note>
-For explicit `models.providers["amazon-bedrock"]` entries, FengMing can still resolve Bedrock env-marker auth early from AWS env markers such as `AWS_BEARER_TOKEN_BEDROCK` without forcing full runtime auth loading. The actual model-call auth path still uses the AWS SDK default chain.
-</Note>
-
-<AccordionGroup>
-  <Accordion title="Discovery config options">
-    Config options live under `plugins.entries.amazon-bedrock.config.discovery`:
-
-    ```json5
-    {
-      plugins: {
-        entries: {
-          "amazon-bedrock": {
-            config: {
-              discovery: {
-                enabled: true,
-                region: "us-east-1",
-                providerFilter: ["anthropic", "amazon"],
-                refreshInterval: 3600,
-                defaultContextWindow: 32000,
-                defaultMaxTokens: 4096,
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-    | Option | Default | Description |
-    | ------ | ------- | ----------- |
-    | `enabled` | auto | In auto mode, FengMing only enables the implicit Bedrock provider when it sees a supported AWS env marker. Set `true` to force discovery. |
-    | `region` | `AWS_REGION` / `AWS_DEFAULT_REGION` / `us-east-1` | AWS region used for discovery API calls. |
-    | `providerFilter` | (all) | Matches Bedrock provider names (for example `anthropic`, `amazon`). |
-    | `refreshInterval` | `3600` | Cache duration in seconds. Set to `0` to disable caching. |
-    | `defaultContextWindow` | `32000` | Context window used for discovered models (override if you know your model limits). |
-    | `defaultMaxTokens` | `4096` | Max output tokens used for discovered models (override if you know your model limits). |
-
-  </Accordion>
-</AccordionGroup>
-
-## Quick setup (AWS path)
-
-This walkthrough creates an IAM role, attaches Bedrock permissions, associates
-the instance profile, and enables FengMing discovery on the EC2 host.
-
-```bash
-# 1. Create IAM role and instance profile
-aws iam create-role --role-name EC2-Bedrock-Access \
-  --assume-role-policy-document '{
-    "Version": "2012-10-17",
-    "Statement": [{
-      "Effect": "Allow",
-      "Principal": {"Service": "ec2.amazonaws.com"},
-      "Action": "sts:AssumeRole"
-    }]
-  }'
-
-aws iam attach-role-policy --role-name EC2-Bedrock-Access \
-  --policy-arn arn:aws:iam::aws:policy/AmazonBedrockFullAccess
-
-aws iam create-instance-profile --instance-profile-name EC2-Bedrock-Access
-aws iam add-role-to-instance-profile \
-  --instance-profile-name EC2-Bedrock-Access \
-  --role-name EC2-Bedrock-Access
-
-# 2. Attach to your EC2 instance
-aws ec2 associate-iam-instance-profile \
-  --instance-id i-xxxxx \
-  --iam-instance-profile Name=EC2-Bedrock-Access
-
-# 3. On the EC2 instance, enable discovery explicitly
-fengming config set plugins.entries.amazon-bedrock.config.discovery.enabled true
-fengming config set plugins.entries.amazon-bedrock.config.discovery.region us-east-1
-
-# 4. Optional: add an env marker if you want auto mode without explicit enable
-echo 'export AWS_PROFILE=default' >> ~/.bashrc
-echo 'export AWS_REGION=us-east-1' >> ~/.bashrc
-source ~/.bashrc
-
-# 5. Verify models are discovered
-fengming models list
-```
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Inference profiles">
-    FengMing discovers **regional and global inference profiles** alongside
-    foundation models. When a profile maps to a known foundation model, the
-    profile inherits that model's capabilities (context window, max tokens,
-    reasoning, vision) and the correct Bedrock request region is injected
-    automatically. This means cross-region Claude profiles work without manual
-    provider overrides.
-
-    Inference profile IDs look like `us.anthropic.claude-opus-4-6-v1:0` (regional)
-    or `anthropic.claude-opus-4-6-v1:0` (global). If the backing model is already
-    in the discovery results, the profile inherits its full capability set;
-    otherwise safe defaults apply.
-
-    No extra configuration is needed. As long as discovery is enabled and the IAM
-    principal has `bedrock:ListInferenceProfiles`, profiles appear alongside
-    foundation models in `fengming models list`.
-
-  </Accordion>
-
-  <Accordion title="Service tier">
-    Some Bedrock models support a `service_tier` parameter to optimize for cost
-    or latency. The following tiers are available:
-
-    | Tier | Description |
-    |------|-------------|
-    | `default` | Standard Bedrock tier |
-    | `flex` | Discounted processing for workloads that can tolerate longer latency |
-    | `priority` | Prioritized processing for latency-sensitive workloads |
-    | `reserved` | Reserved capacity for steady-state workloads |
-
-    Set `serviceTier` (or `service_tier`) via `agents.defaults.params` for
-    Bedrock model requests, or per-model in
-    `agents.defaults.models["<model-key>"].params`:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          params: {
-            serviceTier: "flex", // applies to all models
-          },
-          models: {
-            "amazon-bedrock/mistral.mistral-large-3-675b-instruct": {
-              params: {
-                serviceTier: "priority", // per-model override
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-    Valid values are `default`, `flex`, `priority`, and `reserved`. Not all
-    models support all tiers — if an unsupported tier is requested, Bedrock will
-    return a validation error. Note: the error message is somewhat misleading;
-    it may say "The provided model identifier is invalid" rather than indicating
-    an unsupported service tier. If you see this error, check whether the model
-    supports the requested tier.
-
-  </Accordion>
-
-  <Accordion title="Claude Opus 4.7 temperature">
-    Bedrock rejects the `temperature` parameter for Claude Opus 4.7. FengMing
-    omits `temperature` automatically for any Opus 4.7 Bedrock ref, including
-    foundation model ids, named inference profiles, application inference
-    profiles whose underlying model resolves to Opus 4.7 via
-    `bedrock:GetInferenceProfile`, and dotted `opus-4.7` variants with
-    optional region prefixes (`us.`, `eu.`, `ap.`, `apac.`, `au.`, `jp.`,
-    `global.`). No config knob is required, and the omission applies to both
-    the request options object and the `inferenceConfig` payload field.
-  </Accordion>
-
-  <Accordion title="Guardrails">
-    You can apply [Amazon Bedrock Guardrails](https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails.html)
-    to all Bedrock model invocations by adding a `guardrail` object to the
-    `amazon-bedrock` plugin config. Guardrails let you enforce content filtering,
-    topic denial, word filters, sensitive information filters, and contextual
-    grounding checks.
-
-    ```json5
-    {
-      plugins: {
-        entries: {
-          "amazon-bedrock": {
-            config: {
-              guardrail: {
-                guardrailIdentifier: "abc123", // guardrail ID or full ARN
-                guardrailVersion: "1", // version number or "DRAFT"
-                streamProcessingMode: "sync", // optional: "sync" or "async"
-                trace: "enabled", // optional: "enabled", "disabled", or "enabled_full"
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-    | Option | Required | Description |
-    | ------ | -------- | ----------- |
-    | `guardrailIdentifier` | Yes | Guardrail ID (e.g. `abc123`) or full ARN (e.g. `arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123`). |
-    | `guardrailVersion` | Yes | Published version number, or `"DRAFT"` for the working draft. |
-    | `streamProcessingMode` | No | `"sync"` or `"async"` for guardrail evaluation during streaming. If omitted, Bedrock uses its default. |
-    | `trace` | No | `"enabled"` or `"enabled_full"` for debugging; omit or set `"disabled"` for production. |
-
-    <Warning>
-    The IAM principal used by the gateway must have the `bedrock:ApplyGuardrail` permission in addition to the standard invoke permissions.
-    </Warning>
-
-  </Accordion>
-
-  <Accordion title="Embeddings for memory search">
-    Bedrock can also serve as the embedding provider for
-    [memory search](/concepts/memory-search). This is configured separately from the
-    inference provider -- set `agents.defaults.memorySearch.provider` to `"bedrock"`:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          memorySearch: {
-            provider: "bedrock",
-            model: "amazon.titan-embed-text-v2:0", // default
-          },
-        },
-      },
-    }
-    ```
-
-    Bedrock embeddings use the same AWS SDK credential chain as inference (instance
-    roles, SSO, access keys, shared config, and web identity). No API key is
-    needed. Set `memorySearch.provider: "bedrock"` explicitly to use Bedrock
-    embeddings.
-
-    Supported embedding models include Amazon Titan Embed (v1, v2), Amazon Nova
-    Embed, Cohere Embed (v3, v4), and TwelveLabs Marengo. See
-    [Memory configuration reference -- Bedrock](/reference/memory-config#bedrock-embedding-config)
-    for the full model list and dimension options.
-
-  </Accordion>
-
-  <Accordion title="Notes and caveats">
-    - Bedrock requires **model access** enabled in your AWS account/region.
-    - Automatic discovery needs the `bedrock:ListFoundationModels` and
-      `bedrock:ListInferenceProfiles` permissions.
-    - If you rely on auto mode, set one of the supported AWS auth env markers on the
-      gateway host. If you prefer IMDS/shared-config auth without env markers, set
-      `plugins.entries.amazon-bedrock.config.discovery.enabled: true`.
-    - FengMing surfaces the credential source in this order: `AWS_BEARER_TOKEN_BEDROCK`,
-      then `AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, then `AWS_PROFILE`, then the
-      default AWS SDK chain.
-    - Reasoning support depends on the model; check the Bedrock model card for
-      current capabilities.
-    - If you prefer a managed key flow, you can also place an OpenAI-compatible
-      proxy in front of Bedrock and configure it as an OpenAI provider instead.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Memory search" href="/concepts/memory-search" icon="magnifying-glass">
-    Bedrock embeddings for memory search configuration.
-  </Card>
-  <Card title="Memory config reference" href="/reference/memory-config#bedrock-embedding-config" icon="database">
-    Full Bedrock embedding model list and dimension options.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>

package/docs/providers/cerebras.md

@@ -1,130 +0,0 @@
----
-summary: "Cerebras setup (auth + model selection)"
-title: "Cerebras"
-read_when:
-  - You want to use Cerebras with FengMing
-  - You need the Cerebras API key env var or CLI auth choice
----
-
-[Cerebras](https://www.cerebras.ai) provides high-speed OpenAI-compatible inference on custom inference hardware. FengMing includes a bundled Cerebras provider plugin with a static four-model catalog.
-
-| Property        | Value                                    |
-| --------------- | ---------------------------------------- |
-| Provider id     | `cerebras`                               |
-| Plugin          | bundled, `enabledByDefault: true`        |
-| Auth env var    | `CEREBRAS_API_KEY`                       |
-| Onboarding flag | `--auth-choice cerebras-api-key`         |
-| Direct CLI flag | `--cerebras-api-key <key>`               |
-| API             | OpenAI-compatible (`openai-completions`) |
-| Base URL        | `https://api.cerebras.ai/v1`             |
-| Default model   | `cerebras/zai-glm-4.7`                   |
-
-## Getting started
-
-<Steps>
-  <Step title="Get an API key">
-    Create an API key in the [Cerebras Cloud Console](https://cloud.cerebras.ai).
-  </Step>
-  <Step title="Run onboarding">
-    <CodeGroup>
-
-```bash Onboarding
-fengming onboard --auth-choice cerebras-api-key
-```
-
-```bash Direct flag
-fengming onboard --non-interactive \
-  --auth-choice cerebras-api-key \
-  --cerebras-api-key "$CEREBRAS_API_KEY"
-```
-
-```bash Env only
-export CEREBRAS_API_KEY=csk-...
-```
-
-    </CodeGroup>
-
-  </Step>
-  <Step title="Verify models are available">
-    ```bash
-    fengming models list --provider cerebras
-    ```
-
-    The list should include all four bundled models. If `CEREBRAS_API_KEY` is unresolved, `fengming models status --json` reports the missing credential under `auth.unusableProfiles`.
-
-  </Step>
-</Steps>
-
-## Non-interactive setup
-
-```bash
-fengming onboard --non-interactive \
-  --mode local \
-  --auth-choice cerebras-api-key \
-  --cerebras-api-key "$CEREBRAS_API_KEY"
-```
-
-## Built-in catalog
-
-FengMing ships a static Cerebras catalog that mirrors the public OpenAI-compatible endpoint. All four models share a 128k context and 8,192 max-output tokens.
-
-| Model ref                                 | Name                 | Reasoning | Notes                                  |
-| ----------------------------------------- | -------------------- | --------- | -------------------------------------- |
-| `cerebras/zai-glm-4.7`                    | Z.ai GLM 4.7         | yes       | Default model; preview reasoning model |
-| `cerebras/gpt-oss-120b`                   | GPT OSS 120B         | yes       | Production reasoning model             |
-| `cerebras/qwen-3-235b-a22b-instruct-2507` | Qwen 3 235B Instruct | no        | Preview non-reasoning model            |
-| `cerebras/llama3.1-8b`                    | Llama 3.1 8B         | no        | Production speed-focused model         |
-
-<Warning>
-  Cerebras marks `zai-glm-4.7` and `qwen-3-235b-a22b-instruct-2507` as preview models, and `llama3.1-8b` plus `qwen-3-235b-a22b-instruct-2507` are documented for deprecation on May 27, 2026. Check Cerebras' supported-models page before relying on them for production workloads.
-</Warning>
-
-## Manual config
-
-The bundled plugin usually means you only need the API key. Use explicit `models.providers.cerebras` config when you want to override model metadata or run in `mode: "merge"` against the static catalog:
-
-```json5
-{
-  env: { CEREBRAS_API_KEY: "csk-..." },
-  agents: {
-    defaults: {
-      model: { primary: "cerebras/zai-glm-4.7" },
-    },
-  },
-  models: {
-    mode: "merge",
-    providers: {
-      cerebras: {
-        baseUrl: "https://api.cerebras.ai/v1",
-        apiKey: "${CEREBRAS_API_KEY}",
-        api: "openai-completions",
-        models: [
-          { id: "zai-glm-4.7", name: "Z.ai GLM 4.7" },
-          { id: "gpt-oss-120b", name: "GPT OSS 120B" },
-        ],
-      },
-    },
-  },
-}
-```
-
-<Note>
-  If the Gateway runs as a daemon (launchd, systemd, Docker), make sure `CEREBRAS_API_KEY` is available to that process — for example in `~/.fengming/.env` or through `env.shellEnv`. A key exported only in an interactive shell will not help a managed service unless the env is imported separately.
-</Note>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Thinking modes" href="/tools/thinking" icon="brain">
-    Reasoning effort levels for the two reasoning-capable Cerebras models.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/config-agents#agent-defaults" icon="gear">
-    Agent defaults and model configuration.
-  </Card>
-  <Card title="Models FAQ" href="/help/faq-models" icon="circle-question">
-    Auth profiles, switching models, and resolving "no profile" errors.
-  </Card>
-</CardGroup>

package/docs/providers/chutes.md

@@ -1,153 +0,0 @@
----
-summary: "Chutes setup (OAuth or API key, model discovery, aliases)"
-title: "Chutes"
-read_when:
-  - You want to use Chutes with FengMing
-  - You need the OAuth or API key setup path
-  - You want the default model, aliases, or discovery behavior
----
-
-[Chutes](https://chutes.ai) exposes open-source model catalogs through an
-OpenAI-compatible API. FengMing supports both browser OAuth and direct API-key
-auth for the bundled `chutes` provider.
-
-| Property | Value                        |
-| -------- | ---------------------------- |
-| Provider | `chutes`                     |
-| API      | OpenAI-compatible            |
-| Base URL | `https://llm.chutes.ai/v1`   |
-| Auth     | OAuth or API key (see below) |
-
-## Getting started
-
-<Tabs>
-  <Tab title="OAuth">
-    <Steps>
-      <Step title="Run the OAuth onboarding flow">
-        ```bash
-        fengming onboard --auth-choice chutes
-        ```
-        FengMing launches the browser flow locally, or shows a URL + redirect-paste
-        flow on remote/headless hosts. OAuth tokens auto-refresh through FengMing 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
-        fengming 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, FengMing queries the Chutes catalog with that
-credential and uses the discovered models. If discovery fails, FengMing falls
-back to a bundled static catalog so onboarding and startup still work.
-
-## Default aliases
-
-FengMing registers three convenience aliases for the bundled Chutes catalog:
-
-| Alias           | Target model                                          |
-| --------------- | ----------------------------------------------------- |
-| `chutes-fast`   | `chutes/zai-org/GLM-4.7-FP8`                          |
-| `chutes-pro`    | `chutes/deepseek-ai/DeepSeek-V3.2-TEE`                |
-| `chutes-vision` | `chutes/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>
-
-## Related
-
-<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>