fengming 0.3.10 → 0.3.12

package/docs/providers/alibaba.md

@@ -1,158 +0,0 @@
----
-summary: "Alibaba Model Studio Wan video generation in FengMing"
-title: "Alibaba Model Studio"
-read_when:
-  - You want to use Alibaba Wan video generation in FengMing
-  - You need Model Studio or DashScope API key setup for video generation
----
-
-FengMing ships a bundled `alibaba` plugin that registers a video-generation provider for Wan models on Alibaba Model Studio (the international name for DashScope). The plugin is enabled by default; you only need to set an API key.
-
-| Property         | Value                                                                           |
-| ---------------- | ------------------------------------------------------------------------------- |
-| Provider id      | `alibaba`                                                                       |
-| Plugin           | bundled, `enabledByDefault: true`                                               |
-| Auth env vars    | `MODELSTUDIO_API_KEY` → `DASHSCOPE_API_KEY` → `QWEN_API_KEY` (first match wins) |
-| Onboarding flag  | `--auth-choice alibaba-model-studio-api-key`                                    |
-| Direct CLI flag  | `--alibaba-model-studio-api-key <key>`                                          |
-| Default model    | `alibaba/wan2.6-t2v`                                                            |
-| Default base URL | `https://dashscope-intl.aliyuncs.com`                                           |
-
-## Getting started
-
-<Steps>
-  <Step title="Set an API key">
-    Use onboarding to store the key against the `alibaba` provider:
-
-    ```bash
-    fengming onboard --auth-choice alibaba-model-studio-api-key
-    ```
-
-    Or pass the key directly during install/onboarding:
-
-    ```bash
-    fengming onboard --alibaba-model-studio-api-key <your-key>
-    ```
-
-    Or export any of the accepted env vars before starting the Gateway:
-
-    ```bash
-    export MODELSTUDIO_API_KEY=sk-...
-    # or DASHSCOPE_API_KEY=...
-    # or QWEN_API_KEY=...
-    ```
-
-  </Step>
-  <Step title="Set a default video model">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "alibaba/wan2.6-t2v",
-          },
-        },
-      },
-    }
-    ```
-  </Step>
-  <Step title="Verify the provider is configured">
-    ```bash
-    fengming models list --provider alibaba
-    ```
-
-    The list should include all five bundled Wan models. If `MODELSTUDIO_API_KEY` is unresolved, `fengming models status --json` reports the missing credential under `auth.unusableProfiles`.
-
-  </Step>
-</Steps>
-
-<Note>
-  The Alibaba plugin and the [Qwen plugin](/providers/qwen) both authenticate against DashScope and accept overlapping env vars. Use `alibaba/...` model ids to drive the dedicated Wan video surface; use `qwen/...` ids when you want Qwen's chat, embedding, or media-understanding surface.
-</Note>
-
-## Built-in Wan models
-
-| Model ref                  | Mode                      |
-| -------------------------- | ------------------------- |
-| `alibaba/wan2.6-t2v`       | Text-to-video (default)   |
-| `alibaba/wan2.6-i2v`       | Image-to-video            |
-| `alibaba/wan2.6-r2v`       | Reference-to-video        |
-| `alibaba/wan2.6-r2v-flash` | Reference-to-video (fast) |
-| `alibaba/wan2.7-r2v`       | Reference-to-video        |
-
-## Capabilities and limits
-
-The bundled provider mirrors DashScope's Wan video API caps. All three modes share the same per-request video count and duration cap; only the input shape differs.
-
-| Mode               | Max output videos | Max input images | Max input videos | Max duration | Supported controls                                        |
-| ------------------ | ----------------- | ---------------- | ---------------- | ------------ | --------------------------------------------------------- |
-| Text-to-video      | 1                 | n/a              | n/a              | 10 s         | `size`, `aspectRatio`, `resolution`, `audio`, `watermark` |
-| Image-to-video     | 1                 | 1                | n/a              | 10 s         | `size`, `aspectRatio`, `resolution`, `audio`, `watermark` |
-| Reference-to-video | 1                 | n/a              | 4                | 10 s         | `size`, `aspectRatio`, `resolution`, `audio`, `watermark` |
-
-When a request omits `durationSeconds`, the provider sends DashScope's accepted default of **5 seconds**. Set `durationSeconds` explicitly on the [video generation tool](/tools/video-generation) to extend up to 10 s.
-
-<Warning>
-  Reference image and video inputs must be remote `http(s)` URLs. Local file paths are not accepted by DashScope's reference modes; upload to object storage first or use the [media tool](/tools/media-overview) flow that already produces a public URL.
-</Warning>
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Override the DashScope base URL">
-    The provider defaults to the international DashScope endpoint. To target the China-region endpoint, set:
-
-    ```json5
-    {
-      models: {
-        providers: {
-          alibaba: {
-            baseUrl: "https://dashscope.aliyuncs.com",
-          },
-        },
-      },
-    }
-    ```
-
-    The provider strips trailing slashes before constructing AIGC task URLs.
-
-  </Accordion>
-
-  <Accordion title="Auth env priority">
-    FengMing resolves the Alibaba API key from environment variables in this order, taking the first non-empty value:
-
-    1. `MODELSTUDIO_API_KEY`
-    2. `DASHSCOPE_API_KEY`
-    3. `QWEN_API_KEY`
-
-    Configured `auth.profiles` entries (set via `fengming models auth login`) override env-var resolution. See [Auth profiles in the models FAQ](/help/faq-models#what-is-an-auth-profile) for profile rotation, cooldown, and override mechanics.
-
-  </Accordion>
-
-  <Accordion title="Relationship to the Qwen plugin">
-    Both bundled plugins talk to DashScope and accept overlapping API keys. Use:
-
-    - `alibaba/wan*.*` ids to drive the dedicated Wan video provider documented on this page.
-    - `qwen/*` ids for Qwen chat, embedding, and media understanding (see [Qwen](/providers/qwen)).
-
-    Setting `MODELSTUDIO_API_KEY` once authenticates both plugins because the auth env var list intentionally overlaps; you do not need to onboard each plugin separately.
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Qwen" href="/providers/qwen" icon="microchip">
-    Qwen chat, embedding, and media-understanding setup on the same DashScope auth.
-  </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/anthropic.md

@@ -1,381 +0,0 @@
----
-summary: "Use Anthropic Claude via API keys or Claude CLI in FengMing"
-read_when:
-  - You want to use Anthropic models in FengMing
-title: "Anthropic"
----
-
-Anthropic builds the **Claude** model family. FengMing supports two auth routes:
-
-- **API key** — direct Anthropic API access with usage-based billing (`anthropic/*` models)
-- **Claude CLI** — reuse an existing Claude Code login on the same host
-
-<Warning>
-FengMing's Claude CLI backend runs the installed Claude Code CLI in
-non-interactive print mode. Anthropic's current Claude Code docs describe
-`claude -p` as Agent SDK/programmatic usage. Starting June 15, 2026, Anthropic
-says subscription-plan `claude -p` usage no longer draws from normal Claude
-plan limits; it draws from a separate monthly Agent SDK credit first, then from
-usage credits at standard API rates when those credits are enabled.
-
-Interactive Claude Code still draws from the signed-in Claude plan limits. API
-key auth remains direct pay-as-you-go API billing. For long-lived gateway hosts,
-shared automation, and predictable production spend, use an Anthropic API key.
-
-Anthropic's current public docs:
-
-- [Claude Code CLI reference](https://code.claude.com/docs/en/cli-usage)
-- [Use the Claude Agent SDK with your Claude plan](https://support.claude.com/en/articles/15036540-use-the-claude-agent-sdk-with-your-claude-plan)
-- [Use Claude Code with your Pro or Max plan](https://support.claude.com/en/articles/11145838-use-claude-code-with-your-pro-or-max-plan)
-- [Use Claude Code with your Team or Enterprise plan](https://support.claude.com/en/articles/11845131-using-claude-code-with-your-team-or-enterprise-plan)
-- [Manage Claude Code costs](https://code.claude.com/docs/en/costs)
-
-</Warning>
-
-## Getting started
-
-<Tabs>
-  <Tab title="API key">
-    **Best for:** standard API access and usage-based billing.
-
-    <Steps>
-      <Step title="Get your API key">
-        Create an API key in the [Anthropic Console](https://console.anthropic.com/).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        fengming onboard
-        # choose: Anthropic API key
-        ```
-
-        Or pass the key directly:
-
-        ```bash
-        fengming onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        fengming models list --provider anthropic
-        ```
-      </Step>
-    </Steps>
-
-    ### Config example
-
-    ```json5
-    {
-      env: { ANTHROPIC_API_KEY: "example-anthropic-key-not-real" },
-      agents: { defaults: { model: { primary: "anthropic/claude-opus-4-8" } } },
-    }
-    ```
-
-  </Tab>
-
-  <Tab title="Claude CLI">
-    **Best for:** reusing an existing Claude CLI login without a separate API key.
-
-    <Steps>
-      <Step title="Ensure Claude CLI is installed and logged in">
-        Verify with:
-
-        ```bash
-        claude --version
-        ```
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        fengming onboard
-        # choose: Claude CLI
-        ```
-
-        FengMing detects and reuses the existing Claude CLI credentials.
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        fengming models list --provider anthropic
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    Setup and runtime details for the Claude CLI backend are in [CLI Backends](/gateway/cli-backends).
-    </Note>
-
-    <Warning>
-    Claude CLI reuse expects the FengMing process to run on the same host as the
-    Claude CLI login. Container installs such as [Podman](/install/podman) do
-    not mount host `~/.claude` into setup or runtime; use an Anthropic API key
-    there, or choose a provider with FengMing-managed OAuth such as
-    [OpenAI Codex](/providers/openai).
-    </Warning>
-
-    ### Config example
-
-    Prefer the canonical Anthropic model ref plus a CLI runtime override:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "anthropic/claude-opus-4-8" },
-          models: {
-            "anthropic/claude-opus-4-8": {
-              agentRuntime: { id: "claude-cli" },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-    Legacy `claude-cli/claude-opus-4-7` model refs still work for
-    compatibility, but new config should keep provider/model selection as
-    `anthropic/*` and put the execution backend in provider/model runtime policy.
-
-    ### Billing and `claude -p`
-
-    FengMing uses Claude Code's non-interactive `claude -p` path for Claude CLI
-    runs. Anthropic currently treats that path as Agent SDK/programmatic usage:
-
-    - Until June 15, 2026, subscription-plan handling follows Anthropic's active
-      Claude Code rules for the signed-in account.
-    - Starting June 15, 2026, subscription-plan `claude -p` usage draws from the
-      user's monthly Agent SDK credit first, then from usage credits at standard
-      API rates if usage credits are enabled.
-    - Console/API-key logins use pay-as-you-go API billing and do not receive
-      the subscription Agent SDK credit.
-
-    Anthropic can change Claude Code billing and rate-limit behavior without an
-    FengMing release. Check `claude auth status`, `/status`, and
-    Anthropic's linked docs when billing predictability matters.
-
-    <Tip>
-    For shared production automation, use an Anthropic API key instead of
-    Claude CLI. FengMing also supports subscription-style options from
-    [OpenAI Codex](/providers/openai), [Qwen Cloud](/providers/qwen),
-    [MiniMax](/providers/minimax), and [Z.AI / GLM](/providers/zai).
-    </Tip>
-
-  </Tab>
-</Tabs>
-
-## Thinking defaults (Claude 4.8 and 4.6)
-
-Claude Opus 4.8 keeps thinking off by default in FengMing. When you explicitly enable adaptive thinking with `/think high|xhigh|max`, FengMing sends Anthropic's Opus 4.8 effort values; Claude 4.6 models default to `adaptive`.
-
-Override per-message with `/think:<level>` or in model params:
-
-```json5
-{
-  agents: {
-    defaults: {
-      models: {
-        "anthropic/claude-opus-4-8": {
-          params: { thinking: "high" },
-        },
-      },
-    },
-  },
-}
-```
-
-<Note>
-Related Anthropic docs:
-- [Adaptive thinking](https://platform.claude.com/docs/en/build-with-claude/adaptive-thinking)
-- [Extended thinking](https://platform.claude.com/docs/en/build-with-claude/extended-thinking)
-
-</Note>
-
-## Prompt caching
-
-FengMing supports Anthropic's prompt caching feature for API-key auth.
-
-| Value               | Cache duration | Description                            |
-| ------------------- | -------------- | -------------------------------------- |
-| `"short"` (default) | 5 minutes      | Applied automatically for API-key auth |
-| `"long"`            | 1 hour         | Extended cache                         |
-| `"none"`            | No caching     | Disable prompt caching                 |
-
-```json5
-{
-  agents: {
-    defaults: {
-      models: {
-        "anthropic/claude-opus-4-6": {
-          params: { cacheRetention: "long" },
-        },
-      },
-    },
-  },
-}
-```
-
-<AccordionGroup>
-  <Accordion title="Per-agent cache overrides">
-    Use model-level params as your baseline, then override specific agents via `agents.list[].params`:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "anthropic/claude-opus-4-6" },
-          models: {
-            "anthropic/claude-opus-4-6": {
-              params: { cacheRetention: "long" },
-            },
-          },
-        },
-        list: [
-          { id: "research", default: true },
-          { id: "alerts", params: { cacheRetention: "none" } },
-        ],
-      },
-    }
-    ```
-
-    Config merge order:
-
-    1. `agents.defaults.models["provider/model"].params`
-    2. `agents.list[].params` (matching `id`, overrides by key)
-
-    This lets one agent keep a long-lived cache while another agent on the same model disables caching for bursty/low-reuse traffic.
-
-  </Accordion>
-
-  <Accordion title="Bedrock Claude notes">
-    - Anthropic Claude models on Bedrock (`amazon-bedrock/*anthropic.claude*`) accept `cacheRetention` pass-through when configured.
-    - Non-Anthropic Bedrock models are forced to `cacheRetention: "none"` at runtime.
-    - API-key smart defaults also seed `cacheRetention: "short"` for Claude-on-Bedrock refs when no explicit value is set.
-
-  </Accordion>
-</AccordionGroup>
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Fast mode">
-    FengMing's shared `/fast` toggle supports direct Anthropic traffic (API-key and OAuth to `api.anthropic.com`).
-
-    | Command | Maps to |
-    |---------|---------|
-    | `/fast on` | `service_tier: "auto"` |
-    | `/fast off` | `service_tier: "standard_only"` |
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "anthropic/claude-sonnet-4-6": {
-              params: { fastMode: true },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-    <Note>
-    - Only injected for direct `api.anthropic.com` requests. Proxy routes leave `service_tier` untouched.
-    - Explicit `serviceTier` or `service_tier` params override `/fast` when both are set.
-    - On accounts without Priority Tier capacity, `service_tier: "auto"` may resolve to `standard`.
-
-    </Note>
-
-  </Accordion>
-
-  <Accordion title="Media understanding (image and PDF)">
-    The bundled Anthropic plugin registers image and PDF understanding. FengMing
-    auto-resolves media capabilities from the configured Anthropic auth — no
-    additional config is needed.
-
-    | Property        | Value                 |
-    | --------------- | --------------------- |
-    | Default model   | `claude-opus-4-8`     |
-    | Supported input | Images, PDF documents |
-
-    When an image or PDF is attached to a conversation, FengMing automatically
-    routes it through the Anthropic media understanding provider.
-
-  </Accordion>
-
-  <Accordion title="1M context window">
-    Anthropic's 1M context window is available on GA-capable Claude 4.x models
-    such as Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6. FengMing sizes those models at
-    1M automatically:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "anthropic/claude-opus-4-6": {},
-          },
-        },
-      },
-    }
-    ```
-
-    Older configs can keep `params.context1m: true`, but FengMing no longer sends
-    the retired `context-1m-2025-08-07` beta header. Older `anthropicBeta` config
-    entries with that value are ignored during request header resolution and
-    unsupported older Claude models stay on their normal context window.
-
-    `params.context1m: true` also applies to the Claude CLI backend
-    (`claude-cli/*`) for eligible GA-capable Opus and Sonnet models, preserving
-    the runtime context window for those CLI sessions to match the direct-API
-    behavior.
-
-    <Warning>
-    Requires long-context access on your Anthropic credential. OAuth/subscription token auth keeps its required Anthropic beta headers, but FengMing strips the retired 1M beta header if it remains in older config.
-    </Warning>
-
-  </Accordion>
-
-  <Accordion title="Claude Opus 4.8 1M context">
-    `anthropic/claude-opus-4-8` and its `claude-cli` variant have a 1M context
-    window by default — no `params.context1m: true` needed.
-  </Accordion>
-</AccordionGroup>
-
-## Troubleshooting
-
-<AccordionGroup>
-  <Accordion title="401 errors / token suddenly invalid">
-    Anthropic token auth expires and can be revoked. For new setups, use an Anthropic API key instead.
-  </Accordion>
-
-  <Accordion title='No API key found for provider "anthropic"'>
-    Anthropic auth is **per agent** — new agents do not inherit the main agent's keys. Re-run onboarding for that agent (or configure an API key on the gateway host), then verify with `fengming models status`.
-  </Accordion>
-
-  <Accordion title='No credentials found for profile "anthropic:default"'>
-    Run `fengming models status` to see which auth profile is active. Re-run onboarding, or configure an API key for that profile path.
-  </Accordion>
-
-  <Accordion title="No available auth profile (all in cooldown)">
-    Check `fengming models status --json` for `auth.unusableProfiles`. Anthropic rate-limit cooldowns can be model-scoped, so a sibling Anthropic model may still be usable. Add another Anthropic profile or wait for cooldown.
-  </Accordion>
-</AccordionGroup>
-
-<Note>
-More help: [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Note>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="CLI backends" href="/gateway/cli-backends" icon="terminal">
-    Claude CLI backend setup and runtime details.
-  </Card>
-  <Card title="Prompt caching" href="/reference/prompt-caching" icon="database">
-    How prompt caching works across providers.
-  </Card>
-  <Card title="OAuth and auth" href="/gateway/authentication" icon="key">
-    Auth details and credential reuse rules.
-  </Card>
-</CardGroup>

package/docs/providers/arcee.md

@@ -1,144 +0,0 @@
----
-summary: "Arcee AI setup (auth + model selection)"
-title: "Arcee AI"
-read_when:
-  - You want to use Arcee AI with FengMing
-  - You need the API key env var or CLI auth choice
----
-
-[Arcee AI](https://arcee.ai) provides access to the Trinity family of mixture-of-experts models through an OpenAI-compatible API. All Trinity models are Apache 2.0 licensed.
-
-Arcee AI models can be accessed directly via the Arcee platform or through [OpenRouter](/providers/openrouter).
-
-| Property | Value                                                                                 |
-| -------- | ------------------------------------------------------------------------------------- |
-| Provider | `arcee`                                                                               |
-| Auth     | `ARCEEAI_API_KEY` (direct) or `OPENROUTER_API_KEY` (via OpenRouter)                   |
-| API      | OpenAI-compatible                                                                     |
-| Base URL | `https://api.arcee.ai/api/v1` (direct) or `https://openrouter.ai/api/v1` (OpenRouter) |
-
-## Getting started
-
-<Tabs>
-  <Tab title="Direct (Arcee platform)">
-    <Steps>
-      <Step title="Get an API key">
-        Create an API key at [Arcee AI](https://chat.arcee.ai/).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        fengming onboard --auth-choice arceeai-api-key
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "arcee/trinity-large-thinking" },
-            },
-          },
-        }
-        ```
-      </Step>
-    </Steps>
-  </Tab>
-
-  <Tab title="Via OpenRouter">
-    <Steps>
-      <Step title="Get an API key">
-        Create an API key at [OpenRouter](https://openrouter.ai/keys).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        fengming onboard --auth-choice arceeai-openrouter
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "arcee/trinity-large-thinking" },
-            },
-          },
-        }
-        ```
-
-        The same model refs work for both direct and OpenRouter setups (for example `arcee/trinity-large-thinking`).
-      </Step>
-    </Steps>
-
-  </Tab>
-</Tabs>
-
-## Non-interactive setup
-
-<Tabs>
-  <Tab title="Direct (Arcee platform)">
-    ```bash
-    fengming onboard --non-interactive \
-      --mode local \
-      --auth-choice arceeai-api-key \
-      --arceeai-api-key "$ARCEEAI_API_KEY"
-    ```
-  </Tab>
-
-  <Tab title="Via OpenRouter">
-    ```bash
-    fengming onboard --non-interactive \
-      --mode local \
-      --auth-choice arceeai-openrouter \
-      --openrouter-api-key "$OPENROUTER_API_KEY"
-    ```
-  </Tab>
-</Tabs>
-
-## Built-in catalog
-
-FengMing currently ships this bundled Arcee catalog:
-
-| Model ref                      | Name                   | Input | Context | Cost (in/out per 1M) | Notes                                     |
-| ------------------------------ | ---------------------- | ----- | ------- | -------------------- | ----------------------------------------- |
-| `arcee/trinity-large-thinking` | Trinity Large Thinking | text  | 256K    | $0.25 / $0.90        | Default model; reasoning enabled          |
-| `arcee/trinity-large-preview`  | Trinity Large Preview  | text  | 128K    | $0.25 / $1.00        | General-purpose; 400B params, 13B active  |
-| `arcee/trinity-mini`           | Trinity Mini 26B       | text  | 128K    | $0.045 / $0.15       | Fast and cost-efficient; function calling |
-
-<Tip>
-The onboarding preset sets `arcee/trinity-large-thinking` as the default model.
-</Tip>
-
-## Supported features
-
-| Feature                                       | Supported                                    |
-| --------------------------------------------- | -------------------------------------------- |
-| Streaming                                     | Yes                                          |
-| Tool use / function calling                   | Yes (Trinity Mini, Trinity Large Preview)    |
-| Structured output (JSON mode and JSON schema) | Yes                                          |
-| Extended thinking                             | Yes (Trinity Large Thinking; tools disabled) |
-
-<AccordionGroup>
-  <Accordion title="Environment note">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `ARCEEAI_API_KEY`
-    (or `OPENROUTER_API_KEY`) is available to that process (for example, in
-    `~/.fengming/.env` or via `env.shellEnv`).
-  </Accordion>
-
-  <Accordion title="OpenRouter routing">
-    When using Arcee models via OpenRouter, the same `arcee/*` model refs apply.
-    FengMing handles routing transparently based on your auth choice. See the
-    [OpenRouter provider docs](/providers/openrouter) for OpenRouter-specific
-    configuration details.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="OpenRouter" href="/providers/openrouter" icon="shuffle">
-    Access Arcee models and many others through a single API key.
-  </Card>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-</CardGroup>