StepFun OpenClaw Plugin

Official StepFun provider plugin for OpenClaw.

This plugin adds two model providers:

• stepfun for standard StepFun endpoints
• stepfun-plan for Step Plan endpoints

Both providers use the same API key env var, STEPFUN_API_KEY, with setup choices for China and International regions.

Install

After the package is published:

openclaw plugins install clawhub:@stepfun-ai/stepfun-openclaw-plugin

For local development:

openclaw plugins install .

Restart the gateway after install so OpenClaw reloads the plugin.

What It Supports

• Standard StepFun endpoints:
  • https://api.stepfun.com/v1
  • https://api.stepfun.ai/v1
• Step Plan endpoints:
  • https://api.stepfun.com/step_plan/v1
  • https://api.stepfun.ai/step_plan/v1
• Provider ids:
  • stepfun
  • stepfun-plan
• Shared API key env var:
  • STEPFUN_API_KEY

Current Models

• stepfun
  • step-3.5-flash
• stepfun-plan
  • step-3.5-flash

Local Validation

For an isolated local test run, set both OPENCLAW_STATE_DIR and OPENCLAW_CONFIG_PATH:

tmp="$(mktemp -d)"
printf '{}\n' > "$tmp/openclaw.json"
OPENCLAW_STATE_DIR="$tmp" \
OPENCLAW_CONFIG_PATH="$tmp/openclaw.json" \
openclaw plugins install .

Then verify the plugin and its providers:

OPENCLAW_STATE_DIR="$tmp" \
OPENCLAW_CONFIG_PATH="$tmp/openclaw.json" \
STEPFUN_API_KEY=test-key \
openclaw plugins inspect @stepfun-ai/stepfun-openclaw-plugin --json

The inspect output should show both provider ids:

• stepfun
• stepfun-plan

Notes

• Env-only discovery defaults to the International endpoints when only STEPFUN_API_KEY is present.
• Setup writes auth profiles for both provider ids, so the plugin does not rely on core auth normalization for stepfun-plan.