* docs(secrets): remove retired web credential paths * refactor(web): remove retired provider compatibility paths * refactor(providers): delete retired compatibility routes * refactor(secrets): remove retired credential aliases * refactor(plugin-sdk): delete retired compatibility surfaces * docs(plugin-sdk): remove retired migration guidance * chore(plugin-sdk): refresh rebased surface budgets * chore(plugin-sdk): refresh API removal baseline * refactor(compat): migrate retired internal callers * chore(plugin-sdk): refresh current-main baselines * test(config): migrate plugin-owned secret assertions * test(gateway): narrow plugin secret refs * fix(plugin-sdk): preserve private boundary type identity * chore(compat): remove stale sweep references * chore(lint): lower max-lines budget * refactor(secrets): remove unused web helper * build(plugin-sdk): drop removed compat entries * chore(plugin-sdk): refresh rebased API baseline * chore(plugin-sdk): use Linux API baseline hash * fix(plugin-sdk): preserve private bundled build entries * fix(plugin-sdk): package private runtime facades * fix(plugins): preserve external credential contracts
3.3 KiB
summary, read_when, title
| summary | read_when | title | |||
|---|---|---|---|---|---|
| MiniMax Search via the Token Plan search API |
|
MiniMax search |
OpenClaw supports MiniMax as a web_search provider through the MiniMax
Token Plan search API. It returns structured search results with titles, URLs,
snippets, and related queries.
Get a Token Plan credential
Create or copy a MiniMax Token Plan key from [MiniMax Platform](https://platform.minimax.io/user-center/basic-information/interface-key). OAuth setups can reuse `MINIMAX_OAUTH_TOKEN` instead. Set `MINIMAX_CODE_PLAN_KEY` in the Gateway environment, or configure via:```bash
openclaw configure --section web
```
OpenClaw also accepts MINIMAX_CODING_API_KEY, MINIMAX_OAUTH_TOKEN, and
MINIMAX_API_KEY as env aliases, checked in that order after
MINIMAX_CODE_PLAN_KEY. MINIMAX_API_KEY should point at a search-enabled
Token Plan credential; ordinary MiniMax model API keys may not be accepted by
the Token Plan search endpoint.
Config
{
plugins: {
entries: {
minimax: {
config: {
webSearch: {
apiKey: "sk-cp-...", // optional if a MiniMax Token Plan env var is set
region: "global", // or "cn"
},
},
},
},
},
tools: {
web: {
search: {
provider: "minimax",
},
},
},
}
Environment alternative: set MINIMAX_CODE_PLAN_KEY, MINIMAX_CODING_API_KEY,
MINIMAX_OAUTH_TOKEN, or MINIMAX_API_KEY in the Gateway environment.
For a gateway install, put it in ~/.openclaw/.env.
Region selection
MiniMax Search uses these endpoints:
- Global:
https://api.minimax.io/v1/coding_plan/search - CN:
https://api.minimaxi.com/v1/coding_plan/search
If plugins.entries.minimax.config.webSearch.region is unset, OpenClaw resolves
the region in this order:
- Plugin-owned
webSearch.region MINIMAX_API_HOSTmodels.providers.minimax.baseUrlmodels.providers.minimax-portal.baseUrl
That means CN onboarding or MINIMAX_API_HOST=https://api.minimaxi.com/...
automatically keeps MiniMax Search on the CN host too.
Even when you authenticated MiniMax through the OAuth minimax-portal path,
web search still registers as provider id minimax; the OAuth provider base URL
is used as a region hint for CN/global host selection, and MINIMAX_OAUTH_TOKEN
can satisfy the MiniMax Search bearer credential.
Supported parameters
| Parameter | Type | Constraints | Description |
|---|---|---|---|
query |
string | required | Search query string. |
count |
integer | 1-10, default 5 | Number of results to return. OpenClaw trims the returned list to this size. |
Provider-specific filters are not currently supported.
Related
- Web Search overview -- all providers and auto-detection
- MiniMax -- model, image, speech, and auth setup