Providers

Tencent Cloud (TokenHub / TokenPlan)

Install the official Tencent Cloud provider plugin to access Tencent Hy3 through two endpoints — TokenHub (tencent-tokenhub) and TokenPlan (tencent-tokenplan) — using an OpenAI-compatible API.

Property Value
Provider ids tencent-tokenhub, tencent-tokenplan
Package @openclaw/tencent-provider
TokenHub auth env var TOKENHUB_API_KEY
TokenPlan auth env var TOKENPLAN_API_KEY
TokenHub onboarding flag --auth-choice tokenhub-api-key
TokenPlan onboarding flag --auth-choice tokenplan-api-key
TokenHub direct CLI flag --tokenhub-api-key <key>
TokenPlan direct CLI flag --tokenplan-api-key <key>
API OpenAI-compatible (openai-completions)
TokenHub base URL https://tokenhub.tencentmaas.com/v1
TokenHub global base URL https://tokenhub-intl.tencentmaas.com/v1 (override)
TokenPlan base URL https://api.lkeap.cloud.tencent.com/plan/v3
Default model tencent-tokenhub/hy3

Quick start

  • Create a Tencent API key

    Create an API key for Tencent Cloud TokenHub and TokenPlan. If you choose a limited access scope for the key, include hy3 (and hy3 preview if you plan to use it on TokenHub) in the allowed models.

  • Run onboarding

    TokenHub onboarding
    openclaw onboard --auth-choice tokenhub-api-key
    TokenHub direct flag
    openclaw onboard --non-interactive \--auth-choice tokenhub-api-key \--tokenhub-api-key "$TOKENHUB_API_KEY"
    TokenPlan onboarding
    openclaw onboard --auth-choice tokenplan-api-key
    TokenPlan direct flag
    openclaw onboard --non-interactive \--auth-choice tokenplan-api-key \--tokenplan-api-key "$TOKENPLAN_API_KEY"
    Env only
    export TOKENHUB_API_KEY=...export TOKENPLAN_API_KEY=...
  • Verify the model

    bash
    openclaw models list --provider tencent-tokenhubopenclaw models list --provider tencent-tokenplan
  • Non-interactive setup

    bash
    # TokenHubopenclaw onboard --non-interactive \  --mode local \  --auth-choice tokenhub-api-key \  --tokenhub-api-key "$TOKENHUB_API_KEY" \  --skip-health \  --accept-risk # TokenPlanopenclaw onboard --non-interactive \  --mode local \  --auth-choice tokenplan-api-key \  --tokenplan-api-key "$TOKENPLAN_API_KEY" \  --skip-health \  --accept-risk

    Built-in catalog

    Model ref Name Input Context Max output Notes
    tencent-tokenhub/hy3-preview hy3 preview (TokenHub) text 256,000 64,000 reasoning-enabled
    tencent-tokenhub/hy3 hy3 (TokenHub) text 256,000 64,000 reasoning-enabled
    tencent-tokenplan/hy3 hy3 (TokenPlan) text 256,000 64,000 reasoning-enabled

    hy3 is Tencent Hunyuan's large MoE language model for reasoning, long-context instruction following, code, and agent workflows. Tencent's OpenAI-compatible examples use hy3 as the model id and support standard chat-completions tool calling plus reasoning_effort.

    Advanced configuration

    Endpoint override

    OpenClaw's built-in catalog uses Tencent Cloud's https://tokenhub.tencentmaas.com/v1 endpoint. Override it only if your TokenHub account or region requires a different one:

    bash
    openclaw config set models.providers.tencent-tokenhub.baseUrl "https://your-endpoint/v1"
    Environment availability for the daemon

    If the Gateway runs as a managed service (launchd, systemd, Docker), TOKENHUB_API_KEY and TOKENPLAN_API_KEY must be visible to that process. Set them in ~/.openclaw/.env or via env.shellEnv so launchd, systemd, or Docker exec environments can read them.

    Was this useful?
    On this page

    On this page