durar-ai 2026.4.4

package/docs/providers/qianfan.md

@@ -0,0 +1,90 @@
+---
+summary: "Use Qianfan's unified API to access many models in Durar"
+read_when:
+  - You want a single API key for many LLMs
+  - You need Baidu Qianfan setup guidance
+title: "Qianfan"
+---
+
+# Qianfan Provider Guide
+
+Qianfan is Baidu's MaaS platform, provides a **unified API** that routes requests to many models behind a single
+endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switching the base URL.
+
+## Prerequisites
+
+1. A Baidu Cloud account with Qianfan API access
+2. An API key from the Qianfan console
+3. Durar installed on your system
+
+## Getting Your API Key
+
+1. Visit the [Qianfan Console](https://console.bce.baidu.com/qianfan/ais/console/apiKey)
+2. Create a new application or select an existing one
+3. Generate an API key (format: `bce-v3/ALTAK-...`)
+4. Copy the API key for use with Durar
+
+## CLI setup
+
+```bash
+Durar onboard --auth-choice qianfan-api-key
+```
+
+## Config snippet
+
+```json5
+{
+  env: { QIANFAN_API_KEY: "bce-v3/ALTAK-..." },
+  agents: {
+    defaults: {
+      model: { primary: "qianfan/deepseek-v3.2" },
+      models: {
+        "qianfan/deepseek-v3.2": { alias: "QIANFAN" },
+      },
+    },
+  },
+  models: {
+    providers: {
+      qianfan: {
+        baseUrl: "https://qianfan.baidubce.com/v2",
+        api: "openai-completions",
+        models: [
+          {
+            id: "deepseek-v3.2",
+            name: "DEEPSEEK V3.2",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 98304,
+            maxTokens: 32768,
+          },
+          {
+            id: "ernie-5.0-thinking-preview",
+            name: "ERNIE-5.0-Thinking-Preview",
+            reasoning: true,
+            input: ["text", "image"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 119000,
+            maxTokens: 64000,
+          },
+        ],
+      },
+    },
+  },
+}
+```
+
+## Notes
+
+- Default bundled model ref: `qianfan/deepseek-v3.2`
+- Default base URL: `https://qianfan.baidubce.com/v2`
+- Bundled catalog currently includes `deepseek-v3.2` and `ernie-5.0-thinking-preview`
+- Add or override `models.providers.qianfan` only when you need custom base URL or model metadata
+- Qianfan runs through the OpenAI-compatible transport path, not native OpenAI request shaping
+
+## Related Documentation
+
+- [Durar Configuration](/gateway/configuration)
+- [Model Providers](/concepts/model-providers)
+- [Agent Setup](/concepts/agent)
+- [Qianfan API Documentation](https://cloud.baidu.com/doc/qianfan-api/s/3m7of64lb)

package/docs/providers/qwen.md

@@ -0,0 +1,128 @@
+summary: "Use Qwen Cloud via Durar's bundled qwen provider"
+read_when:
+
+- You want to use Qwen with Durar
+- You previously used Qwen OAuth
+  title: "Qwen"
+
+---
+
+# Qwen
+
+<Warning>
+
+**Qwen OAuth has been removed.** The free-tier OAuth integration
+(`qwen-portal`) that used `portal.qwen.ai` endpoints is no longer available.
+See [Issue #49557](https://github.com/openclaw/openclaw/issues/49557) for
+background.
+
+</Warning>
+
+## Recommended: Qwen Cloud
+
+Durar 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 and keeps legacy `modelstudio` ids working as a
+compatibility alias.
+
+- Provider: `qwen`
+- Preferred env var: `QWEN_API_KEY`
+- Also accepted for compatibility: `MODELSTUDIO_API_KEY`, `DASHSCOPE_API_KEY`
+- API style: OpenAI-compatible
+
+If you want `qwen3.6-plus`, prefer the **Standard (pay-as-you-go)** endpoint.
+Coding Plan support can lag behind the public catalog.
+
+```bash
+# Global Coding Plan endpoint
+Durar onboard --auth-choice qwen-api-key
+
+# China Coding Plan endpoint
+Durar onboard --auth-choice qwen-api-key-cn
+
+# Global Standard (pay-as-you-go) endpoint
+Durar onboard --auth-choice qwen-standard-api-key
+
+# China Standard (pay-as-you-go) endpoint
+Durar onboard --auth-choice qwen-standard-api-key-cn
+```
+
+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.
+
+After onboarding, set a default model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "qwen/qwen3.5-plus" },
+    },
+  },
+}
+```
+
+## Capability plan
+
+The `qwen` extension 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
+
+## Multimodal add-ons
+
+The `qwen` extension now also exposes:
+
+- 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`
+
+These multimodal surfaces 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`
+
+For video generation, Durar 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.
+
+For video generation, set a default model explicitly:
+
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: { primary: "qwen/wan2.6-t2v" },
+    },
+  },
+}
+```
+
+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`
+
+See [Qwen / Model Studio](/providers/qwen_modelstudio) for endpoint-level detail
+and compatibility notes.

package/docs/providers/qwen_modelstudio.md

@@ -0,0 +1,137 @@
+title: "Qwen / Model Studio"
+summary: "Endpoint detail for the bundled qwen provider and its legacy modelstudio compatibility surface"
+read_when:
+
+- You want endpoint-level detail for Qwen Cloud / Alibaba DashScope
+- You need the env var compatibility story for the qwen provider
+- You want to use the Standard (pay-as-you-go) or Coding Plan endpoint
+
+---
+
+# Qwen / Model Studio (Alibaba Cloud)
+
+This page documents the endpoint mapping behind Durar's bundled `qwen`
+provider. The provider keeps `modelstudio` provider ids, auth-choice ids, and
+model refs working as compatibility aliases while `qwen` becomes the canonical
+surface.
+
+<Info>
+
+If you need **`qwen3.6-plus`**, prefer **Standard (pay-as-you-go)**. Coding
+Plan availability can lag behind the public Model Studio catalog, and the
+Coding Plan API can reject a model until it appears in your plan's supported
+model list.
+
+</Info>
+
+- Provider: `qwen` (legacy alias: `modelstudio`)
+- Auth: `QWEN_API_KEY`
+- Also accepted: `MODELSTUDIO_API_KEY`, `DASHSCOPE_API_KEY`
+- API: OpenAI-compatible
+
+## Quick start
+
+### Standard (pay-as-you-go)
+
+```bash
+# China endpoint
+Durar onboard --auth-choice qwen-standard-api-key-cn
+
+# Global/Intl endpoint
+Durar onboard --auth-choice qwen-standard-api-key
+```
+
+### Coding Plan (subscription)
+
+```bash
+# China endpoint
+Durar onboard --auth-choice qwen-api-key-cn
+
+# Global/Intl endpoint
+Durar onboard --auth-choice qwen-api-key
+```
+
+Legacy `modelstudio-*` auth-choice ids still work as compatibility aliases, but
+the canonical onboarding ids are the `qwen-*` choices shown above.
+
+After onboarding, set a default model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "qwen/qwen3.5-plus" },
+    },
+  },
+}
+```
+
+## 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`          |
+
+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.
+
+Native Model Studio endpoints advertise streaming usage compatibility on the
+shared `openai-completions` transport. Durar 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.
+
+## Get your API key
+
+- **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)
+
+## Built-in catalog
+
+Durar currently ships this bundled Qwen catalog:
+
+| 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                            |
+
+Availability can still vary by endpoint and billing plan even when a model is
+present in the bundled catalog.
+
+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`
+
+## 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.
+
+## Environment note
+
+If the Gateway runs as a daemon (launchd/systemd), make sure
+`QWEN_API_KEY` is available to that process (for example, in
+`~/.Durar/.env` or via `env.shellEnv`).

package/docs/providers/sglang.md

@@ -0,0 +1,115 @@
+---
+summary: "Run Durar with SGLang (OpenAI-compatible self-hosted server)"
+read_when:
+  - You want to run Durar against a local SGLang server
+  - You want OpenAI-compatible /v1 endpoints with your own models
+title: "SGLang"
+---
+
+# SGLang
+
+SGLang can serve open-source models via an **OpenAI-compatible** HTTP API.
+Durar can connect to SGLang using the `openai-completions` API.
+
+Durar can also **auto-discover** available models from SGLang when you opt
+in with `SGLANG_API_KEY` (any value works if your server does not enforce auth)
+and you do not define an explicit `models.providers.sglang` entry.
+
+## Quick start
+
+1. Start 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`
+
+2. Opt in (any value works if no auth is configured):
+
+```bash
+export SGLANG_API_KEY="sglang-local"
+```
+
+3. Run onboarding and choose `SGLang`, or set a model directly:
+
+```bash
+Durar onboard
+```
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "sglang/your-model-id" },
+    },
+  },
+}
+```
+
+## Model discovery (implicit provider)
+
+When `SGLANG_API_KEY` is set (or an auth profile exists) and you **do not**
+define `models.providers.sglang`, Durar will query:
+
+- `GET http://127.0.0.1:30000/v1/models`
+
+and convert the returned IDs into model entries.
+
+If you set `models.providers.sglang` explicitly, auto-discovery is skipped and
+you must define models manually.
+
+## 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,
+          },
+        ],
+      },
+    },
+  },
+}
+```
+
+## Troubleshooting
+
+- Check the server is reachable:
+
+```bash
+curl http://127.0.0.1:30000/v1/models
+```
+
+- 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`.
+
+## Proxy-style behavior
+
+SGLang is treated as a proxy-style OpenAI-compatible `/v1` backend, not a
+native OpenAI endpoint.
+
+- native OpenAI-only request shaping does not apply here
+- no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- hidden Durar attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on custom SGLang base URLs

package/docs/providers/stepfun.md

@@ -0,0 +1,152 @@
+---
+summary: "Use StepFun models with Durar"
+read_when:
+  - You want StepFun models in Durar
+  - You need StepFun setup guidance
+title: "StepFun"
+---
+
+# StepFun
+
+Durar includes a bundled StepFun provider plugin with two provider ids:
+
+- `stepfun` for the standard endpoint
+- `stepfun-plan` for the Step Plan endpoint
+
+The built-in catalogs currently differ by surface:
+
+- Standard: `step-3.5-flash`
+- Step Plan: `step-3.5-flash`, `step-3.5-flash-2603`
+
+## Region and endpoint overview
+
+- China standard endpoint: `https://api.stepfun.com/v1`
+- Global standard endpoint: `https://api.stepfun.ai/v1`
+- China Step Plan endpoint: `https://api.stepfun.com/step_plan/v1`
+- Global Step Plan endpoint: `https://api.stepfun.ai/step_plan/v1`
+- Auth env var: `STEPFUN_API_KEY`
+
+Use a China key with the `.com` endpoints and a global key with the `.ai`
+endpoints.
+
+## CLI setup
+
+Interactive setup:
+
+```bash
+Durar onboard
+```
+
+Choose one of these auth choices:
+
+- `stepfun-standard-api-key-cn`
+- `stepfun-standard-api-key-intl`
+- `stepfun-plan-api-key-cn`
+- `stepfun-plan-api-key-intl`
+
+Non-interactive examples:
+
+```bash
+Durar onboard --auth-choice stepfun-standard-api-key-intl --stepfun-api-key "$STEPFUN_API_KEY"
+Durar onboard --auth-choice stepfun-plan-api-key-intl --stepfun-api-key "$STEPFUN_API_KEY"
+```
+
+## Model refs
+
+- Standard default model: `stepfun/step-3.5-flash`
+- Step Plan default model: `stepfun-plan/step-3.5-flash`
+- Step Plan alternate model: `stepfun-plan/step-3.5-flash-2603`
+
+## Built-in catalogs
+
+Standard (`stepfun`):
+
+| Model ref                | Context | Max output | Notes                  |
+| ------------------------ | ------- | ---------- | ---------------------- |
+| `stepfun/step-3.5-flash` | 262,144 | 65,536     | Default standard model |
+
+Step Plan (`stepfun-plan`):
+
+| Model ref                          | Context | Max output | Notes                      |
+| ---------------------------------- | ------- | ---------- | -------------------------- |
+| `stepfun-plan/step-3.5-flash`      | 262,144 | 65,536     | Default Step Plan model    |
+| `stepfun-plan/step-3.5-flash-2603` | 262,144 | 65,536     | Additional Step Plan model |
+
+## Config snippets
+
+Standard provider:
+
+```json5
+{
+  env: { STEPFUN_API_KEY: "your-key" },
+  agents: { defaults: { model: { primary: "stepfun/step-3.5-flash" } } },
+  models: {
+    mode: "merge",
+    providers: {
+      stepfun: {
+        baseUrl: "https://api.stepfun.ai/v1",
+        api: "openai-completions",
+        apiKey: "${STEPFUN_API_KEY}",
+        models: [
+          {
+            id: "step-3.5-flash",
+            name: "Step 3.5 Flash",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 65536,
+          },
+        ],
+      },
+    },
+  },
+}
+```
+
+Step Plan provider:
+
+```json5
+{
+  env: { STEPFUN_API_KEY: "your-key" },
+  agents: { defaults: { model: { primary: "stepfun-plan/step-3.5-flash" } } },
+  models: {
+    mode: "merge",
+    providers: {
+      "stepfun-plan": {
+        baseUrl: "https://api.stepfun.ai/step_plan/v1",
+        api: "openai-completions",
+        apiKey: "${STEPFUN_API_KEY}",
+        models: [
+          {
+            id: "step-3.5-flash",
+            name: "Step 3.5 Flash",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 65536,
+          },
+          {
+            id: "step-3.5-flash-2603",
+            name: "Step 3.5 Flash 2603",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 65536,
+          },
+        ],
+      },
+    },
+  },
+}
+```
+
+## Notes
+
+- The provider is bundled with Durar, so there is no separate plugin install step.
+- `step-3.5-flash-2603` is currently exposed only on `stepfun-plan`.
+- A single auth flow writes region-matched profiles for both `stepfun` and `stepfun-plan`, so both surfaces can be discovered together.
+- Use `Durar models list` and `Durar models set <provider/model>` to inspect or switch models.
+- For the broader provider overview, see [Model providers](/concepts/model-providers).