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@bcd1dec3dc

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-22 05:46:57 +00:00
parent 237560254b
commit 87ae9b1c27
2 changed files with 15 additions and 45 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": "dc4e97472d4f3d1f8df00a17193952df6f9ade31",
"syncedAt": "2026-04-22T05:34:11.225Z"
"sha": "bcd1dec3dce1a7eb311af637103addadd639e695",
"syncedAt": "2026-04-22T05:46:56.641Z"
}

56
docs/providers/tencent.md
View File

@ -1,64 +1,40 @@
---
title: "Tencent Cloud (TokenHub + Token Plan)"
summary: "Tencent Cloud TokenHub and Token Plan setup (separate keys)"
title: "Tencent Cloud (TokenHub)"
summary: "Tencent Cloud TokenHub setup"
read_when:
- You want to use Tencent Hy models with OpenClaw
- You need the TokenHub API key or Token Plan (LKEAP) setup
- You need the TokenHub API key setup
---
# Tencent Cloud (TokenHub + Token Plan)
# Tencent Cloud (TokenHub)
The Tencent Cloud provider gives access to Tencent Hy models via two endpoints
with separate API keys:
The Tencent Cloud provider gives access to Tencent Hy models via the TokenHub
endpoint (`tencent-tokenhub`).
- **TokenHub** (`tencent-tokenhub`) — call Hy via Tencent TokenHub Gateway
- **Token Plan** (`tencent-token-plan`) — call Hy via the LKEAP
Token Plan endpoint
Both providers use OpenAI-compatible APIs.
The provider uses an OpenAI-compatible API.
## Quick start
TokenHub:
```bash
openclaw onboard --auth-choice tokenhub-api-key
```
Token Plan:
```bash
openclaw onboard --auth-choice tencent-token-plan-api-key
```
## Non-interactive example
```bash
# TokenHub
openclaw onboard --non-interactive \
--mode local \
--auth-choice tokenhub-api-key \
--tokenhub-api-key "$TOKENHUB_API_KEY" \
--skip-health \
--accept-risk
# Token Plan
openclaw onboard --non-interactive \
--mode local \
--auth-choice tencent-token-plan-api-key \
--tencent-token-plan-api-key "$LKEAP_API_KEY" \
--skip-health \
--accept-risk
```
## Providers and endpoints
| Provider | Endpoint | Use case |
| -------------------- | ------------------------------------- | ----------------------- |
| `tencent-tokenhub` | `tokenhub.tencentmaas.com/v1` | Hy via Tencent TokenHub |
| `tencent-token-plan` | `api.lkeap.cloud.tencent.com/plan/v3` | Hy via LKEAP Token Plan |
Each provider uses its own API key. Setup registers only the selected provider.
| Provider | Endpoint | Use case |
| ------------------ | ----------------------------- | ----------------------- |
| `tencent-tokenhub` | `tokenhub.tencentmaas.com/v1` | Hy via Tencent TokenHub |
## Available models
@ -66,25 +42,19 @@ Each provider uses its own API key. Setup registers only the selected provider.
- **hy3-preview** — Hy3 preview (256K context, reasoning, default)
### tencent-token-plan
- **hy3-preview** — Hy3 preview (256K context, reasoning, default)
## Notes
- TokenHub model refs use `tencent-tokenhub/<modelId>`. Token Plan model refs
use `tencent-token-plan/<modelId>`.
- TokenHub model refs use `tencent-tokenhub/<modelId>`.
- Override pricing and context metadata in `models.providers` if needed.
## Environment note
If the Gateway runs as a daemon (launchd/systemd), make sure `TOKENHUB_API_KEY`
or `LKEAP_API_KEY` is available to that process (for example, in
`~/.openclaw/.env` or via `env.shellEnv`).
is available to that process (for example, in `~/.openclaw/.env` or via
`env.shellEnv`).
## Related documentation
- [OpenClaw Configuration](/configuration)
- [Model Providers](/concepts/model-providers)
- [Tencent TokenHub](https://cloud.tencent.com/document/product/1823/130050)
- [Tencent Token Plan API](https://cloud.tencent.com/document/product/1823/130060)