Model providers
Using StepFun with OpenClaw
Browse more in Model providers.
All model providers guides →This guide walks you through configuring StepFun as a model provider in OpenClaw, including both the standard and Step Plan endpoints. 5-flash` are available.
By the end, your agents will be able to call StepFun models through OpenClaw with a working config you can customize.
Prerequisites
- ✓An active StepFun account with an API key that works against either the `.ai` (global) or `.com` (China) endpoints.
- ✓An existing OpenClaw installation with the `openclaw` CLI available in your shell.
- ✓Network access from your OpenClaw environment to `https://api.stepfun.ai` or `https://api.stepfun.com` depending on your region.
Steps
- 1
Understand StepFun provider ids and endpoints
OpenClaw bundles StepFun as two separate providers: `stepfun` for the standard endpoint and `stepfun-plan` for the Step Plan endpoint. You need to decide which surface you want to use and match it to the correct base URL and region so your `STEPFUN_API_KEY` works.
textStandard | `https://api.stepfun.com/v1` | `https://api.stepfun.ai/v1` Step Plan | `https://api.stepfun.com/step_plan/v1` | `https://api.stepfun.ai/step_plan/v1` - 2
Choose your StepFun standard endpoint region
For general-purpose use, configure the standard StepFun provider first. com` endpoint.
text| Auth choice | Endpoint | Region | | `stepfun-standard-api-key-intl` | `https://api.stepfun.ai/v1` | International | | `stepfun-standard-api-key-cn` | `https://api.stepfun.com/v1` | China | - 3
Run onboarding for StepFun standard
Use the OpenClaw onboarding flow to register your StepFun standard credentials. This writes a region-matched profile so the `stepfun` provider and its models are discoverable by the CLI and your agents.
bashopenclaw onboard --auth-choice stepfun-standard-api-key-intl - 4
Run onboarding for StepFun standard China endpoint if needed
If your StepFun key is for the China region, run onboarding with the China auth choice instead. com` endpoint and avoids authentication failures against the wrong region.
bashopenclaw onboard --auth-choice stepfun-standard-api-key-cn - 5
Use non-interactive onboarding for StepFun standard
In CI or scripted setups, pass your `STEPFUN_API_KEY` directly to the onboarding command. This avoids interactive prompts and keeps your configuration reproducible.
bashopenclaw onboard --auth-choice stepfun-standard-api-key-intl \ --stepfun-api-key "$STEPFUN_API_KEY" - 6
Verify StepFun standard models are available
After onboarding, list models for the `stepfun` provider to confirm OpenClaw can see the catalog. 5-flash` model and any others you configured.
bashopenclaw models list --provider stepfun - 7
Choose your Step Plan endpoint region
If you want Step Plan reasoning models, configure the `stepfun-plan` provider as well. Again, pick the auth choice that matches your key’s region so OpenClaw hits the correct Step Plan endpoint.
text| Auth choice | Endpoint | Region | | `stepfun-plan-api-key-intl` | `https://api.stepfun.ai/step_plan/v1` | International | | `stepfun-plan-api-key-cn` | `https://api.stepfun.com/step_plan/v1` | China | - 8
Run onboarding for Step Plan
Run the onboarding flow for the Step Plan provider to register your credentials for the reasoning endpoint. This sets up the `stepfun-plan` provider so you can use Step Plan models in your agents.
bashopenclaw onboard --auth-choice stepfun-plan-api-key-intl - 9
Run onboarding for Step Plan China endpoint if needed
If your StepFun Step Plan key is for China, use the China-specific auth choice. com` endpoint and aligned with your account region.
bashopenclaw onboard --auth-choice stepfun-plan-api-key-cn - 10
Use non-interactive onboarding for Step Plan
For automated environments, configure Step Plan non-interactively with your `STEPFUN_API_KEY`. This mirrors the standard setup but targets the Step Plan auth choice.
bashopenclaw onboard --auth-choice stepfun-plan-api-key-intl \ --stepfun-api-key "$STEPFUN_API_KEY" - 11
Verify Step Plan models are available
List models for the `stepfun-plan` provider to confirm the Step Plan catalog is wired up. You should see both the default and alternate Step Plan models if your config matches the docs.
bashopenclaw models list --provider stepfun-plan - 12
Set StepFun standard as the default agent model via config
To make StepFun the default for your agents, add the standard provider config to your OpenClaw config file. 5-flash` as the primary model and defines the provider’s base URL and model metadata.
json{ env: { STEPFUN_API_KEY: "your-key" }, agents: { defaults: { model: { primary: "stepfun/step-3.5-flash" } } }, models: { mode: "merge", providers: { stepfun: { baseUrl: "https://api.stepfun.ai/v1", api: "openai-completions", apiKey: "${STEPFUN_API_KEY}", models: [ { id: "step-3.5-flash", name: "Step 3.5 Flash", reasoning: true, input: ["text"], cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 }, contextWindow: 262144, maxTokens: 65536, }, ], }, }, }, } - 13
Set Step Plan as the default agent model via config
If you prefer the Step Plan reasoning endpoint, configure `stepfun-plan` as the default. 5-flash-2603` model.
json{ env: { STEPFUN_API_KEY: "your-key" }, agents: { defaults: { model: { primary: "stepfun-plan/step-3.5-flash" } } }, models: { mode: "merge", providers: { "stepfun-plan": { baseUrl: "https://api.stepfun.ai/step_plan/v1", api: "openai-completions", apiKey: "${STEPFUN_API_KEY}", models: [ { id: "step-3.5-flash", name: "Step 3.5 Flash", reasoning: true, input: ["text"], cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 }, contextWindow: 262144, maxTokens: 65536, }, { id: "step-3.5-flash-2603", name: "Step 3.5 Flash 2603", reasoning: true, input: ["text"], cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 }, contextWindow: 262144, maxTokens: 65536, }, ], }, }, }, }
Configuration
| Option | Description | Example |
|---|---|---|
| STEPFUN_API_KEY | Authentication key used by both the standard `stepfun` and `stepfun-plan` providers to call the StepFun APIs. | sk-stepfun-abc123 |
| agents.defaults.model.primary | Sets the default model your agents use, such as the StepFun standard or Step Plan model reference. | stepfun/step-3.5-flash |
| models.mode | Controls how your model configuration merges with existing models; the StepFun examples use merge mode. | merge |
| models.providers.stepfun.baseUrl | Base URL for the StepFun standard API endpoint that OpenClaw calls. | https://api.stepfun.ai/v1 |
| models.providers["stepfun-plan"].baseUrl | Base URL for the StepFun Step Plan reasoning endpoint. | https://api.stepfun.ai/step_plan/v1 |
Troubleshooting
After onboarding, `openclaw models list --provider stepfun` shows no models for StepFun.
This usually means the StepFun provider config is missing or not merged. Add the standard provider config block with `mode: "merge"` and the `stepfun` provider definition, then run `openclaw models list --provider stepfun` again.
openclaw models list --provider stepfunStep Plan models like `stepfun-plan/step-3.5-flash-2603` are not available in OpenClaw.
5-flash-2603` model is exposed only on `stepfun-plan`, so you need the Step Plan provider config with that model entry and to onboard using a Step Plan auth choice. Verify with `openclaw models list --provider stepfun-plan` after updating your config.
openclaw models list --provider stepfun-planFrequently asked questions
Powered by Mem0
Add persistent memory to OpenClaw
Official Mem0 plugin for OpenClaw keeps context across chats and tools. Smaller prompts, lower cost, better continuity for your agents.