Skip to main content

​
Fireworks

Fireworks exposes open-weight and routed models through an OpenAI-compatible API. OpenClaw includes a bundled Fireworks provider plugin.
PropertyValue
Providerfireworks
AuthFIREWORKS_API_KEY
APIOpenAI-compatible chat/completions
Base URLhttps://api.fireworks.ai/inference/v1
Default modelfireworks/accounts/fireworks/routers/kimi-k2p5-turbo

​
Getting started

1

Set up Fireworks auth through onboarding

openclaw onboard --auth-choice fireworks-api-key
This stores your Fireworks key in OpenClaw config and sets the Fire Pass starter model as the default.
2

Verify the model is available

openclaw models list --provider fireworks

​
Non-interactive example

For scripted or CI setups, pass all values on the command line: 
openclaw onboard --non-interactive \
  --mode local \
  --auth-choice fireworks-api-key \
  --fireworks-api-key "$FIREWORKS_API_KEY" \
  --skip-health \
  --accept-risk

​
Built-in catalog

Model refNameInputContextMax outputNotes
fireworks/accounts/fireworks/routers/kimi-k2p5-turboKimi K2.5 Turbo (Fire Pass)text,image256,000256,000Default bundled starter model on Fireworks
If Fireworks publishes a newer model such as a fresh Qwen or Gemma release, you can switch to it directly by using its Fireworks model id without waiting for a bundled catalog update.

​
Custom Fireworks model ids

OpenClaw accepts dynamic Fireworks model ids too. Use the exact model or router id shown by Fireworks and prefix it with fireworks/. 
{
  agents: {
    defaults: {
      model: {
        primary: "fireworks/accounts/fireworks/routers/kimi-k2p5-turbo",
      },
    },
  },
}
Every Fireworks model ref in OpenClaw starts with fireworks/ followed by the exact id or router path from the Fireworks platform. For example:
  • Router model: fireworks/accounts/fireworks/routers/kimi-k2p5-turbo
  • Direct model: fireworks/accounts/fireworks/models/<model-name>
OpenClaw strips the fireworks/ prefix when building the API request and sends the remaining path to the Fireworks endpoint.
If the Gateway runs outside your interactive shell, make sure FIREWORKS_API_KEY is available to that process too.
A key sitting only in ~/.profile will not help a launchd/systemd daemon unless that environment is imported there as well. Set the key in ~/.openclaw/.env or via env.shellEnv to ensure the gateway process can read it.

Model selection

Choosing providers, model refs, and failover behavior.

Troubleshooting

General troubleshooting and FAQ.