chore(sync): mirror docs from openclaw/openclaw@fc9648b620

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "b9d26fd1a4101065f682441337da0b08dd7be4d2",
-  "syncedAt": "2026-04-05T11:37:56.654Z"
+  "sha": "fc9648b6201b80909fbec5054c95d31fb18f77df",
+  "syncedAt": "2026-04-05T12:05:28.884Z"
 }

docs/docs.json

@@ -1254,6 +1254,7 @@
                 "pages": [
                   "providers/anthropic",
                   "providers/bedrock",
+                  "providers/bedrock-mantle",
                   "providers/chutes",
                   "providers/claude-max-api-proxy",
                   "providers/cloudflare-ai-gateway",

docs/providers/bedrock-mantle.md

@@ -0,0 +1,91 @@
+---
+summary: "Use Amazon Bedrock Mantle (OpenAI-compatible) models with OpenClaw"
+read_when:
+  - You want to use Bedrock Mantle hosted OSS models with OpenClaw
+  - You need the Mantle OpenAI-compatible endpoint for GPT-OSS, Qwen, Kimi, or GLM
+title: "Amazon Bedrock Mantle"
+---
+
+# Amazon Bedrock Mantle
+
+OpenClaw includes a bundled **Amazon Bedrock Mantle** provider that connects to
+the Mantle OpenAI-compatible endpoint. Mantle hosts open-source and
+third-party models (GPT-OSS, Qwen, Kimi, GLM, and similar) through a standard
+`/v1/chat/completions` surface backed by Bedrock infrastructure.
+
+## What OpenClaw supports
+
+- Provider: `amazon-bedrock-mantle`
+- API: `openai-completions` (OpenAI-compatible)
+- Auth: bearer token via `AWS_BEARER_TOKEN_BEDROCK`
+- Region: `AWS_REGION` or `AWS_DEFAULT_REGION` (default: `us-east-1`)
+
+## Automatic model discovery
+
+When `AWS_BEARER_TOKEN_BEDROCK` is set, OpenClaw automatically discovers
+available Mantle models by querying the region's `/v1/models` endpoint.
+Discovery results are cached for 1 hour.
+
+Supported regions: `us-east-1`, `us-east-2`, `us-west-2`, `ap-northeast-1`,
+`ap-south-1`, `ap-southeast-3`, `eu-central-1`, `eu-west-1`, `eu-west-2`,
+`eu-south-1`, `eu-north-1`, `sa-east-1`.
+
+## Onboarding
+
+1. Set the bearer token on the **gateway host**:
+
+```bash
+export AWS_BEARER_TOKEN_BEDROCK="..."
+# Optional (defaults to us-east-1):
+export AWS_REGION="us-west-2"
+```
+
+2. Verify models are discovered:
+
+```bash
+openclaw models list
+```
+
+Discovered models appear under the `amazon-bedrock-mantle` provider. No
+additional config is required unless you want to override defaults.
+
+## Manual configuration
+
+If you prefer explicit config instead of auto-discovery:
+
+```json5
+{
+  models: {
+    providers: {
+      "amazon-bedrock-mantle": {
+        baseUrl: "https://bedrock-mantle.us-east-1.api.aws/v1",
+        api: "openai-completions",
+        auth: "api-key",
+        apiKey: "env:AWS_BEARER_TOKEN_BEDROCK",
+        models: [
+          {
+            id: "gpt-oss-120b",
+            name: "GPT-OSS 120B",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 32000,
+            maxTokens: 4096,
+          },
+        ],
+      },
+    },
+  },
+}
+```
+
+## Notes
+
+- Mantle requires a bearer token today. Plain IAM credentials (instance roles,
+  SSO, access keys) are not sufficient without a token.
+- The bearer token is the same `AWS_BEARER_TOKEN_BEDROCK` used by the standard
+  [Amazon Bedrock](/providers/bedrock) provider.
+- Reasoning support is inferred from model IDs containing patterns like
+  `thinking`, `reasoner`, or `gpt-oss-120b`.
+- If the Mantle endpoint is unavailable or returns no models, the provider is
+  silently skipped.

docs/providers/bedrock.md

@@ -22,8 +22,8 @@ not an API key.
 ## Automatic model discovery
 
 OpenClaw can automatically discover Bedrock models that support **streaming**
-and **text output**. Discovery uses `bedrock:ListFoundationModels` and is
-cached (default: 1 hour).
+and **text output**. Discovery uses `bedrock:ListFoundationModels` and
+`bedrock:ListInferenceProfiles`, and results are cached (default: 1 hour).
 
 How the implicit provider is enabled:
 
@@ -153,6 +153,7 @@ export AWS_REGION=us-east-1
 - `bedrock:InvokeModel`
 - `bedrock:InvokeModelWithResponseStream`
 - `bedrock:ListFoundationModels` (for automatic discovery)
+- `bedrock:ListInferenceProfiles` (for inference profile discovery)
 
 Or attach the managed policy `AmazonBedrockFullAccess`.
 
@@ -196,10 +197,29 @@ source ~/.bashrc
 openclaw models list
 ```
 
+## Inference profiles
+
+OpenClaw 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 `openclaw models list`.
+
 ## Notes
 
 - Bedrock requires **model access** enabled in your AWS account/region.
-- Automatic discovery needs the `bedrock:ListFoundationModels` permission.
+- 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`.