openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@0793136c63

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-06 00:42:03 +00:00
parent ab31bc7295
commit d2eb948b10
2 changed files with 22 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "098f4eeebbede828e994a10c4973b4d60cf529f4",
"syncedAt": "2026-04-06T00:32:26.256Z"
"sha": "0793136c6361594c889e385dce06a73a0f2b3de6",
"syncedAt": "2026-04-06T00:42:02.598Z"
}

27
docs/providers/bedrock-mantle.md
View File

@ -17,14 +17,17 @@ third-party models (GPT-OSS, Qwen, Kimi, GLM, and similar) through a standard
- Provider: `amazon-bedrock-mantle`
- API: `openai-completions` (OpenAI-compatible)
- Auth: bearer token via `AWS_BEARER_TOKEN_BEDROCK`
- Auth: explicit `AWS_BEARER_TOKEN_BEDROCK` or IAM credential-chain bearer-token generation
- 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.
When `AWS_BEARER_TOKEN_BEDROCK` is set, OpenClaw uses it directly. Otherwise,
OpenClaw attempts to generate a Mantle bearer token from the AWS default
credential chain, including shared credentials/config profiles, SSO, web
identity, and instance or task roles. It then discovers available Mantle
models by querying the region's `/v1/models` endpoint. Discovery results are
cached for 1 hour, and IAM-derived bearer tokens are refreshed hourly.
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`,
@ -32,7 +35,9 @@ Supported regions: `us-east-1`, `us-east-2`, `us-west-2`, `ap-northeast-1`,
## Onboarding
1. Set the bearer token on the **gateway host**:
1. Choose one auth path on the **gateway host**:
Explicit bearer token:
```bash
export AWS_BEARER_TOKEN_BEDROCK="..."
@ -40,6 +45,14 @@ export AWS_BEARER_TOKEN_BEDROCK="..."
export AWS_REGION="us-west-2"
```
IAM credentials:
```bash
# Any AWS SDK-compatible auth source works here, for example:
export AWS_PROFILE="default"
export AWS_REGION="us-west-2"
```
2. Verify models are discovered:
```bash
@ -81,8 +94,8 @@ If you prefer explicit config instead of auto-discovery:
## Notes
- Mantle requires a bearer token today. Plain IAM credentials (instance roles,
SSO, access keys) are not sufficient without a token.
- OpenClaw can mint the Mantle bearer token for you from AWS SDK-compatible
IAM credentials when `AWS_BEARER_TOKEN_BEDROCK` is not set.
- 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