Files
moltbot/docs/tools/minimax-search.md
Jithendra d204be80af feat(tools): add MiniMax as bundled web search provider
Add native MiniMax Search integration via their Coding Plan search API
(POST /v1/coding_plan/search). This brings MiniMax in line with Brave,
Kimi, Grok, Gemini, and other providers that already have bundled web
search support.

- Implement WebSearchProviderPlugin with caching, credential resolution,
  and trusted endpoint wrapping
- Support both global (api.minimax.io) and CN (api.minimaxi.com)
  endpoints, inferred from explicit region config, model provider base
  URL, or minimax-portal OAuth base URL
- Prefer MINIMAX_CODE_PLAN_KEY over MINIMAX_API_KEY in credential
  fallback, matching existing repo precedence
- Accept SecretRef objects for webSearch.apiKey (type: [string, object])
- Register in bundled registry, provider-id compat map, and fast-path
  plugin id list with full alignment test coverage
- Add unit tests for endpoint/region resolution and edge cases

Closes #47927
Related #11399

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-04 19:56:04 +09:00

2.4 KiB

summary, read_when, title
summary read_when title
MiniMax Search via the Coding Plan search API
You want to use MiniMax for web_search
You need a MiniMax Coding Plan key
You want MiniMax CN/global search host guidance
MiniMax Search

MiniMax Search

OpenClaw supports MiniMax as a web_search provider through the MiniMax Coding Plan search API. It returns structured search results with titles, URLs, snippets, and related queries.

Get a Coding Plan key

Create or copy a MiniMax Coding Plan key from [MiniMax Platform](https://platform.minimax.io/user-center/basic-information/interface-key). Set `MINIMAX_CODE_PLAN_KEY` in the Gateway environment, or configure via:
```bash
openclaw configure --section web
```

OpenClaw also accepts MINIMAX_CODING_API_KEY as an env alias. MINIMAX_API_KEY is still read as a compatibility fallback when it already points at a coding-plan token.

Config

{
  plugins: {
    entries: {
      minimax: {
        config: {
          webSearch: {
            apiKey: "sk-cp-...", // optional if MINIMAX_CODE_PLAN_KEY is set
            region: "global", // or "cn"
          },
        },
      },
    },
  },
  tools: {
    web: {
      search: {
        provider: "minimax",
      },
    },
  },
}

Environment alternative: set MINIMAX_CODE_PLAN_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:

  1. tools.web.search.minimax.region / plugin-owned webSearch.region
  2. MINIMAX_API_HOST
  3. models.providers.minimax.baseUrl
  4. models.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.

Supported parameters

MiniMax Search supports:

  • query
  • count (OpenClaw trims the returned result list to the requested count)

Provider-specific filters are not currently supported.