fengming 0.3.10 → 0.3.11

package/docs/providers/qwen.md

@@ -1,364 +0,0 @@
----
-summary: "Use Qwen Cloud via FengMing's bundled qwen provider"
-read_when:
-  - You want to use Qwen with FengMing
-  - You previously used Qwen OAuth
-title: "Qwen"
----
-
-FengMing now treats Qwen as a first-class bundled provider with canonical id
-`qwen`. The bundled provider targets the Qwen Cloud / Alibaba DashScope and
-Coding Plan endpoints, keeps legacy `modelstudio` ids working as a compatibility
-alias, and also exposes the Qwen Portal token flow as provider `qwen-oauth`.
-
-- Provider: `qwen`
-- Portal provider: [`qwen-oauth`](/providers/qwen-oauth)
-- Preferred env var: `QWEN_API_KEY`
-- Also accepted for compatibility: `MODELSTUDIO_API_KEY`, `DASHSCOPE_API_KEY`
-- API style: OpenAI-compatible
-
-<Tip>
-If you want `qwen3.6-plus`, prefer the **Standard (pay-as-you-go)** endpoint.
-Coding Plan support can lag behind the public catalog.
-</Tip>
-
-## Getting started
-
-Choose your plan type and follow the setup steps.
-
-<Tabs>
-  <Tab title="Coding Plan (subscription)">
-    **Best for:** subscription-based access through the Qwen Coding Plan.
-
-    <Steps>
-      <Step title="Get your API key">
-        Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).
-      </Step>
-      <Step title="Run onboarding">
-        For the **Global** endpoint:
-
-        ```bash
-        fengming onboard --auth-choice qwen-api-key
-        ```
-
-        For the **China** endpoint:
-
-        ```bash
-        fengming onboard --auth-choice qwen-api-key-cn
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "qwen/qwen3.5-plus" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        fengming models list --provider qwen
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
-    work as compatibility aliases, but new setup flows should prefer the canonical
-    `qwen-*` auth-choice ids and `qwen/...` model refs. If you define an exact
-    custom `models.providers.modelstudio` entry with another `api` value, that
-    custom provider owns `modelstudio/...` refs instead of the Qwen compatibility
-    alias.
-    </Note>
-
-  </Tab>
-
-  <Tab title="Standard (pay-as-you-go)">
-    **Best for:** pay-as-you-go access through the Standard Model Studio endpoint, including models like `qwen3.6-plus` that may not be available on the Coding Plan.
-
-    <Steps>
-      <Step title="Get your API key">
-        Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).
-      </Step>
-      <Step title="Run onboarding">
-        For the **Global** endpoint:
-
-        ```bash
-        fengming onboard --auth-choice qwen-standard-api-key
-        ```
-
-        For the **China** endpoint:
-
-        ```bash
-        fengming onboard --auth-choice qwen-standard-api-key-cn
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "qwen/qwen3.5-plus" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        fengming models list --provider qwen
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
-    work as compatibility aliases, but new setup flows should prefer the canonical
-    `qwen-*` auth-choice ids and `qwen/...` model refs. If you define an exact
-    custom `models.providers.modelstudio` entry with another `api` value, that
-    custom provider owns `modelstudio/...` refs instead of the Qwen compatibility
-    alias.
-    </Note>
-
-  </Tab>
-
-  <Tab title="Qwen OAuth / Portal">
-    **Best for:** a Qwen Portal token against `https://portal.qwen.ai/v1`.
-
-    See [Qwen OAuth / Portal](/providers/qwen-oauth) for the dedicated provider
-    page and migration notes.
-
-    <Steps>
-      <Step title="Provide your portal token">
-        ```bash
-        fengming onboard --auth-choice qwen-oauth
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "qwen-oauth/qwen3.5-plus" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        fengming models list --provider qwen-oauth
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    `qwen-oauth` uses the same `QWEN_API_KEY` env var name as the DashScope
-    provider, but stores auth under the `qwen-oauth` provider id when configured
-    through FengMing onboarding.
-    </Note>
-
-  </Tab>
-</Tabs>
-
-## Plan types and endpoints
-
-| Plan                       | Region | Auth choice                | Endpoint                                         |
-| -------------------------- | ------ | -------------------------- | ------------------------------------------------ |
-| Standard (pay-as-you-go)   | China  | `qwen-standard-api-key-cn` | `dashscope.aliyuncs.com/compatible-mode/v1`      |
-| Standard (pay-as-you-go)   | Global | `qwen-standard-api-key`    | `dashscope-intl.aliyuncs.com/compatible-mode/v1` |
-| Coding Plan (subscription) | China  | `qwen-api-key-cn`          | `coding.dashscope.aliyuncs.com/v1`               |
-| Coding Plan (subscription) | Global | `qwen-api-key`             | `coding-intl.dashscope.aliyuncs.com/v1`          |
-| Qwen Portal                | Global | `qwen-oauth`               | `portal.qwen.ai/v1`                              |
-
-The provider auto-selects the endpoint based on your auth choice. Canonical
-choices use the `qwen-*` family; `modelstudio-*` remains compatibility-only.
-You can override with a custom `baseUrl` in config.
-
-<Tip>
-**Manage keys:** [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys) |
-**Docs:** [docs.qwencloud.com](https://docs.qwencloud.com/developer-guides/getting-started/introduction)
-</Tip>
-
-## Built-in catalog
-
-FengMing currently ships this bundled Qwen catalog. The configured catalog is
-endpoint-aware: Coding Plan configs omit models that are only known to work on
-the Standard endpoint.
-
-| Model ref                   | Input       | Context   | Notes                                              |
-| --------------------------- | ----------- | --------- | -------------------------------------------------- |
-| `qwen/qwen3.5-plus`         | text, image | 1,000,000 | Default model                                      |
-| `qwen/qwen3.6-plus`         | text, image | 1,000,000 | Prefer Standard endpoints when you need this model |
-| `qwen/qwen3-max-2026-01-23` | text        | 262,144   | Qwen Max line                                      |
-| `qwen/qwen3-coder-next`     | text        | 262,144   | Coding                                             |
-| `qwen/qwen3-coder-plus`     | text        | 1,000,000 | Coding                                             |
-| `qwen/MiniMax-M2.5`         | text        | 1,000,000 | Reasoning enabled                                  |
-| `qwen/glm-5`                | text        | 202,752   | GLM                                                |
-| `qwen/glm-4.7`              | text        | 202,752   | GLM                                                |
-| `qwen/kimi-k2.5`            | text, image | 262,144   | Moonshot AI via Alibaba                            |
-| `qwen-oauth/qwen3.5-plus`   | text, image | 1,000,000 | Qwen Portal default                                |
-
-<Note>
-Availability can still vary by endpoint and billing plan even when a model is
-present in the bundled catalog.
-</Note>
-
-## Thinking Controls
-
-For reasoning-enabled Qwen Cloud models, the bundled provider maps FengMing
-thinking levels to DashScope's top-level `enable_thinking` request flag. Disabled
-thinking sends `enable_thinking: false`; other thinking levels send
-`enable_thinking: true`.
-
-## Multimodal add-ons
-
-The `qwen` plugin also exposes multimodal capabilities on the **Standard**
-DashScope endpoints (not the Coding Plan endpoints):
-
-- **Video understanding** via `qwen-vl-max-latest`
-- **Wan video generation** via `wan2.6-t2v` (default), `wan2.6-i2v`, `wan2.6-r2v`, `wan2.6-r2v-flash`, `wan2.7-r2v`
-
-To use Qwen as the default video provider:
-
-```json5
-{
-  agents: {
-    defaults: {
-      videoGenerationModel: { primary: "qwen/wan2.6-t2v" },
-    },
-  },
-}
-```
-
-<Note>
-See [Video Generation](/tools/video-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Image and video understanding">
-    The bundled Qwen plugin registers media understanding for images and video
-    on the **Standard** DashScope endpoints (not the Coding Plan endpoints).
-
-    | Property      | Value                 |
-    | ------------- | --------------------- |
-    | Model         | `qwen-vl-max-latest`  |
-    | Supported input | Images, video       |
-
-    Media understanding is auto-resolved from the configured Qwen auth — no
-    additional config is needed. Ensure you are using a Standard (pay-as-you-go)
-    endpoint for media understanding support.
-
-  </Accordion>
-
-  <Accordion title="Qwen 3.6 Plus availability">
-    `qwen3.6-plus` is available on the Standard (pay-as-you-go) Model Studio
-    endpoints:
-
-    - China: `dashscope.aliyuncs.com/compatible-mode/v1`
-    - Global: `dashscope-intl.aliyuncs.com/compatible-mode/v1`
-
-    If the Coding Plan endpoints return an "unsupported model" error for
-    `qwen3.6-plus`, switch to Standard (pay-as-you-go) instead of the Coding Plan
-    endpoint/key pair.
-
-    FengMing's bundled Qwen catalog does not advertise `qwen3.6-plus` on Coding
-    Plan endpoints, but explicitly configured `qwen/qwen3.6-plus` entries under
-    `models.providers.qwen.models` are honored on Coding Plan baseUrls so you
-    can opt that model in if Aliyun enables it on your subscription. The
-    upstream API still decides whether the call succeeds.
-
-  </Accordion>
-
-  <Accordion title="Capability plan">
-    The `qwen` plugin is being positioned as the vendor home for the full Qwen
-    Cloud surface, not just coding/text models.
-
-    - **Text/chat models:** bundled now
-    - **Tool calling, structured output, thinking:** inherited from the OpenAI-compatible transport
-    - **Image generation:** planned at the provider-plugin layer
-    - **Image/video understanding:** bundled now on the Standard endpoint
-    - **Speech/audio:** planned at the provider-plugin layer
-    - **Memory embeddings/reranking:** planned through the embedding adapter surface
-    - **Video generation:** bundled now through the shared video-generation capability
-
-  </Accordion>
-
-  <Accordion title="Video generation details">
-    For video generation, FengMing maps the configured Qwen region to the matching
-    DashScope AIGC host before submitting the job:
-
-    - Global/Intl: `https://dashscope-intl.aliyuncs.com`
-    - China: `https://dashscope.aliyuncs.com`
-
-    That means a normal `models.providers.qwen.baseUrl` pointing at either the
-    Coding Plan or Standard Qwen hosts still keeps video generation on the correct
-    regional DashScope video endpoint.
-
-    Current bundled Qwen video-generation limits:
-
-    - Up to **1** output video per request
-    - Up to **1** input image
-    - Up to **4** input videos
-    - Up to **10 seconds** duration
-    - Supports `size`, `aspectRatio`, `resolution`, `audio`, and `watermark`
-    - Reference image/video mode currently requires **remote http(s) URLs**. Local
-      file paths are rejected up front because the DashScope video endpoint does not
-      accept uploaded local buffers for those references.
-
-  </Accordion>
-
-  <Accordion title="Streaming usage compatibility">
-    Native Model Studio endpoints advertise streaming usage compatibility on the
-    shared `openai-completions` transport. FengMing keys that off endpoint
-    capabilities now, so DashScope-compatible custom provider ids targeting the
-    same native hosts inherit the same streaming-usage behavior instead of
-    requiring the built-in `qwen` provider id specifically.
-
-    Native-streaming usage compatibility applies to both the Coding Plan hosts and
-    the Standard DashScope-compatible hosts:
-
-    - `https://coding.dashscope.aliyuncs.com/v1`
-    - `https://coding-intl.dashscope.aliyuncs.com/v1`
-    - `https://dashscope.aliyuncs.com/compatible-mode/v1`
-    - `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
-
-  </Accordion>
-
-  <Accordion title="Multimodal endpoint regions">
-    Multimodal surfaces (video understanding and Wan video generation) use the
-    **Standard** DashScope endpoints, not the Coding Plan endpoints:
-
-    - Global/Intl Standard base URL: `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
-    - China Standard base URL: `https://dashscope.aliyuncs.com/compatible-mode/v1`
-
-  </Accordion>
-
-  <Accordion title="Environment and daemon setup">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `QWEN_API_KEY` is
-    available to that process (for example, in `~/.fengming/.env` or via
-    `env.shellEnv`).
-  </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="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Alibaba (ModelStudio)" href="/providers/alibaba" icon="cloud">
-    Legacy ModelStudio provider and migration notes.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>

package/docs/providers/runway.md

@@ -1,103 +0,0 @@
----
-summary: "Runway video generation setup in FengMing"
-title: "Runway"
-read_when:
-  - You want to use Runway video generation in FengMing
-  - You need the Runway API key/env setup
-  - You want to make Runway the default video provider
----
-
-FengMing ships a bundled `runway` provider for hosted video generation. The plugin is enabled by default and registers the `runway` provider against the `videoGenerationProviders` contract.
-
-| Property        | Value                                                             |
-| --------------- | ----------------------------------------------------------------- |
-| Provider id     | `runway`                                                          |
-| Plugin          | bundled, `enabledByDefault: true`                                 |
-| Auth env vars   | `RUNWAYML_API_SECRET` (canonical) or `RUNWAY_API_KEY`             |
-| Onboarding flag | `--auth-choice runway-api-key`                                    |
-| Direct CLI flag | `--runway-api-key <key>`                                          |
-| API             | Runway task-based video generation (`GET /v1/tasks/{id}` polling) |
-| Default model   | `runway/gen4.5`                                                   |
-
-## Getting started
-
-<Steps>
-  <Step title="Set the API key">
-    ```bash
-    fengming onboard --auth-choice runway-api-key
-    ```
-  </Step>
-  <Step title="Set Runway as the default video provider">
-    ```bash
-    fengming config set agents.defaults.videoGenerationModel.primary "runway/gen4.5"
-    ```
-  </Step>
-  <Step title="Generate a video">
-    Ask the agent to generate a video. Runway will be used automatically.
-  </Step>
-</Steps>
-
-## Supported modes and models
-
-The provider exposes seven Runway models split across three modes. The same model id can serve more than one mode (for example `gen4.5` works for both text-to-video and image-to-video).
-
-| Mode           | Models                                                                 | Reference input         |
-| -------------- | ---------------------------------------------------------------------- | ----------------------- |
-| Text-to-video  | `gen4.5` (default), `veo3.1`, `veo3.1_fast`, `veo3`                    | None                    |
-| Image-to-video | `gen4.5`, `gen4_turbo`, `gen3a_turbo`, `veo3.1`, `veo3.1_fast`, `veo3` | 1 local or remote image |
-| Video-to-video | `gen4_aleph`                                                           | 1 local or remote video |
-
-Local image and video references are supported via data URIs.
-
-| Aspect ratios         | Allowed values                              |
-| --------------------- | ------------------------------------------- |
-| Text-to-video         | `16:9`, `9:16`                              |
-| Image and video edits | `1:1`, `16:9`, `9:16`, `3:4`, `4:3`, `21:9` |
-
-<Warning>
-  Video-to-video currently requires `runway/gen4_aleph`. Other Runway model ids reject video reference inputs.
-</Warning>
-
-<Note>
-  Picking a Runway model id from the wrong column produces an explicit error before the API request leaves FengMing. The provider validates `model` against the mode's allowlist (`TEXT_ONLY_MODELS`, `IMAGE_MODELS`, `VIDEO_MODELS`) in `extensions/runway/video-generation-provider.ts`.
-</Note>
-
-## Configuration
-
-```json5
-{
-  agents: {
-    defaults: {
-      videoGenerationModel: {
-        primary: "runway/gen4.5",
-      },
-    },
-  },
-}
-```
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Environment variable aliases">
-    FengMing recognizes both `RUNWAYML_API_SECRET` (canonical) and `RUNWAY_API_KEY`.
-    Either variable will authenticate the Runway provider.
-  </Accordion>
-
-  <Accordion title="Task polling">
-    Runway uses a task-based API. After submitting a generation request, FengMing
-    polls `GET /v1/tasks/{id}` until the video is ready. No additional
-    configuration is needed for the polling behavior.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared tool parameters, provider selection, and async behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/config-agents#agent-defaults" icon="gear">
-    Agent default settings including video generation model.
-  </Card>
-</CardGroup>

package/docs/providers/senseaudio.md

@@ -1,68 +0,0 @@
----
-summary: "SenseAudio batch speech-to-text for inbound voice notes"
-read_when:
-  - You want SenseAudio speech-to-text for audio attachments
-  - You need the SenseAudio API key env var or audio config path
-title: "SenseAudio"
----
-
-SenseAudio can transcribe inbound audio and voice-note attachments through FengMing's shared `tools.media.audio` pipeline. FengMing posts multipart audio to the OpenAI-compatible transcription endpoint and injects the returned text as `{{Transcript}}` plus an `[Audio]` block.
-
-| Property      | Value                                            |
-| ------------- | ------------------------------------------------ |
-| Provider id   | `senseaudio`                                     |
-| Plugin        | bundled, `enabledByDefault: true`                |
-| Contract      | `mediaUnderstandingProviders` (audio)            |
-| Auth env var  | `SENSEAUDIO_API_KEY`                             |
-| Default model | `senseaudio-asr-pro-1.5-260319`                  |
-| Default URL   | `https://api.senseaudio.cn/v1`                   |
-| Website       | [senseaudio.cn](https://senseaudio.cn)           |
-| Docs          | [senseaudio.cn/docs](https://senseaudio.cn/docs) |
-
-## Getting started
-
-<Steps>
-  <Step title="Set your API key">
-    ```bash
-    export SENSEAUDIO_API_KEY="..."
-    ```
-  </Step>
-  <Step title="Enable the audio provider">
-    ```json5
-    {
-      tools: {
-        media: {
-          audio: {
-            enabled: true,
-            models: [{ provider: "senseaudio", model: "senseaudio-asr-pro-1.5-260319" }],
-          },
-        },
-      },
-    }
-    ```
-  </Step>
-  <Step title="Send a voice note">
-    Send an audio message through any connected channel. FengMing uploads the
-    audio to SenseAudio and uses the transcript in the reply pipeline.
-  </Step>
-</Steps>
-
-## Options
-
-| Option     | Path                                  | Description                         |
-| ---------- | ------------------------------------- | ----------------------------------- |
-| `model`    | `tools.media.audio.models[].model`    | SenseAudio ASR model id             |
-| `language` | `tools.media.audio.models[].language` | Optional language hint              |
-| `prompt`   | `tools.media.audio.prompt`            | Optional transcription prompt       |
-| `baseUrl`  | `tools.media.audio.baseUrl` or model  | Override the OpenAI-compatible base |
-| `headers`  | `tools.media.audio.request.headers`   | Extra request headers               |
-
-<Note>
-SenseAudio is batch STT only in FengMing. Voice Call realtime transcription
-continues to use providers with streaming STT support.
-</Note>
-
-## Related
-
-- [Media understanding (audio)](/nodes/audio)
-- [Model providers](/concepts/model-providers)

package/docs/providers/sglang.md

@@ -1,161 +0,0 @@
----
-summary: "Run FengMing with SGLang (OpenAI-compatible self-hosted server)"
-read_when:
-  - You want to run FengMing against a local SGLang server
-  - You want OpenAI-compatible /v1 endpoints with your own models
-title: "SGLang"
----
-
-SGLang serves open-weight models via an OpenAI-compatible HTTP API. FengMing connects to SGLang using the `openai-completions` provider family with auto-discovery of available models.
-
-| Property                  | Value                                                        |
-| ------------------------- | ------------------------------------------------------------ |
-| Provider id               | `sglang`                                                     |
-| Plugin                    | bundled, `enabledByDefault: true`                            |
-| Auth env var              | `SGLANG_API_KEY` (any non-empty value if server has no auth) |
-| Onboarding flag           | `--auth-choice sglang`                                       |
-| API                       | OpenAI-compatible (`openai-completions`)                     |
-| Default base URL          | `http://127.0.0.1:30000/v1`                                  |
-| Default model placeholder | `sglang/Qwen/Qwen3-8B`                                       |
-| Streaming usage           | Yes (`supportsStreamingUsage: true`)                         |
-| Pricing                   | Marked external-free (`modelPricing.external: false`)        |
-
-FengMing also **auto-discovers** available models from SGLang when you opt in with `SGLANG_API_KEY`. Use `sglang/*` in `agents.defaults.models` to keep discovery dynamic when you also configure a custom SGLang base URL. See [Model discovery (implicit provider)](#model-discovery-implicit-provider) below.
-
-## Getting started
-
-<Steps>
-  <Step title="Start SGLang">
-    Launch SGLang with an OpenAI-compatible server. Your base URL should expose
-    `/v1` endpoints (for example `/v1/models`, `/v1/chat/completions`). SGLang
-    commonly runs on:
-
-    - `http://127.0.0.1:30000/v1`
-
-  </Step>
-  <Step title="Set an API key">
-    Any value works if no auth is configured on your server:
-
-    ```bash
-    export SGLANG_API_KEY="sglang-local"
-    ```
-
-  </Step>
-  <Step title="Run onboarding or set a model directly">
-    ```bash
-    fengming onboard
-    ```
-
-    Or configure the model manually:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "sglang/your-model-id" },
-        },
-      },
-    }
-    ```
-
-  </Step>
-</Steps>
-
-## Model discovery (implicit provider)
-
-When `SGLANG_API_KEY` is set (or an auth profile exists) and you **do not**
-define `models.providers.sglang`, FengMing will query:
-
-- `GET http://127.0.0.1:30000/v1/models`
-
-and convert the returned IDs into model entries.
-
-<Note>
-If you set `models.providers.sglang` explicitly, FengMing uses your declared
-models by default. Add `"sglang/*": {}` to `agents.defaults.models` when you
-want FengMing to query that configured provider's `/models` endpoint and include
-all advertised SGLang models.
-</Note>
-
-## Explicit configuration (manual models)
-
-Use explicit config when:
-
-- SGLang runs on a different host/port.
-- You want to pin `contextWindow`/`maxTokens` values.
-- Your server requires a real API key (or you want to control headers).
-
-```json5
-{
-  models: {
-    providers: {
-      sglang: {
-        baseUrl: "http://127.0.0.1:30000/v1",
-        apiKey: "${SGLANG_API_KEY}",
-        api: "openai-completions",
-        models: [
-          {
-            id: "your-model-id",
-            name: "Local SGLang Model",
-            reasoning: false,
-            input: ["text"],
-            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-            contextWindow: 128000,
-            maxTokens: 8192,
-          },
-        ],
-      },
-    },
-  },
-}
-```
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Proxy-style behavior">
-    SGLang is treated as a proxy-style OpenAI-compatible `/v1` backend, not a
-    native OpenAI endpoint.
-
-    | Behavior | SGLang |
-    |----------|--------|
-    | OpenAI-only request shaping | Not applied |
-    | `service_tier`, Responses `store`, prompt-cache hints | Not sent |
-    | Reasoning-compat payload shaping | Not applied |
-    | Hidden attribution headers (`originator`, `version`, `User-Agent`) | Not injected on custom SGLang base URLs |
-
-  </Accordion>
-
-  <Accordion title="Troubleshooting">
-    **Server not reachable**
-
-    Verify the server is running and responding:
-
-    ```bash
-    curl http://127.0.0.1:30000/v1/models
-    ```
-
-    **Auth errors**
-
-    If requests fail with auth errors, set a real `SGLANG_API_KEY` that matches
-    your server configuration, or configure the provider explicitly under
-    `models.providers.sglang`.
-
-    <Tip>
-    If you run SGLang without authentication, any non-empty value for
-    `SGLANG_API_KEY` is sufficient to opt in to model discovery.
-    </Tip>
-
-  </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="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema including provider entries.
-  </Card>
-</CardGroup>