Use RunAPI in OpenClaw.
RunAPI works as an OpenAI-compatible endpoint for OpenClaw. Paste the setup prompt and the agent writes its own config — provider ID stays local, the model reference maps to runapi/gpt-5.5, and the key lives in RUNAPI_API_KEY.
Configure this OpenClaw workspace to use RunAPI.
Requirements:
- Read the API key from RUNAPI_API_KEY. Do not hardcode the key.
- Add a model provider named runapi.
- Use baseUrl "https://runapi.ai/v1".
- Use api "openai-completions".
- Register provider-local model id "gpt-5.5" with display name "RunAPI GPT 5.5".
- Set the default model to "runapi/gpt-5.5" while keeping existing providers available.
- After editing config, run `openclaw models status` and confirm `runapi/gpt-5.5` appears.
- If RUNAPI_API_KEY is missing, ask me to set it before starting OpenClaw.{
agents: {
defaults: {
model: { primary: "runapi/gpt-5.5" },
models: {
"runapi/gpt-5.5": { alias: "RunAPI GPT 5.5" },
},
},
},
models: {
mode: "merge",
providers: {
runapi: {
baseUrl: "https://runapi.ai/v1",
apiKey: "${RUNAPI_API_KEY}",
api: "openai-completions",
models: [
{
id: "gpt-5.5",
name: "RunAPI GPT 5.5",
reasoning: false,
input: ["text"],
contextWindow: 128000,
maxTokens: 8192,
},
],
},
},
},
}export RUNAPI_API_KEY="runapi_xxx"
openclaw models status
openclaw models set runapi/gpt-5.5
openclawInstall RunAPI in OpenClaw with a prompt
Paste the setup prompt
Copy the prompt from the first tab into OpenClaw. It tells OpenClaw to read RUNAPI_API_KEY, add the runapi provider, and keep existing providers available.
Copy prompt
Review the generated config
OpenClaw should add gpt-5.5 as the provider-local model ID, then select it through the provider-prefixed reference runapi/gpt-5.5.
runapi/gpt-5.5
Verify the selection
Run openclaw models status, switch to the RunAPI model, and start an OpenClaw session. If the model does not appear, confirm the allowlist includes runapi/gpt-5.5.
openclaw models status
Configuration fields
| Field | Value | Purpose |
|---|---|---|
baseUrl |
https://runapi.ai/v1 |
Points OpenClaw at RunAPI's OpenAI-compatible API surface. |
apiKey |
${RUNAPI_API_KEY} |
Reads the RunAPI API key from the environment. |
api |
openai-completions |
Uses the Chat Completions adapter expected by OpenAI-compatible endpoints. |
agents.defaults.model.primary |
runapi/gpt-5.5 |
Selects the RunAPI model as the default model for new OpenClaw sessions. |
Same API key. Images, video, and music.
OpenClaw users typically install a separate GitHub skill for each modality — one for image generation, another for video, a third for music. With RunAPI, the same RUNAPI_API_KEY you already configured for chat also calls 113+ models across image, video, and music endpoints. No extra skills to install.
Image Generation
Generate and edit images through Flux Kontext, Imagen 4, Seedream, GPT Image, and Nano Banana. Send a prompt to the same /v1 endpoint — RunAPI routes to the model you specify.
Browse image modelsVideo Generation
Create video from text or images with Kling 3.0, Seedance 2.0, Veo 3, and Wan 2.7. Same task lifecycle, same callback format, same API key.
Browse video modelsMusic Generation
Generate songs with Suno v4 through v5.5. Pass lyrics, style, and duration — RunAPI returns audio URLs through the standard task polling flow.
Browse music modelsUse any model in OpenClaw
Each guide shows the prompt, curl command, parameters, and FAQ for calling a specific model through RunAPI inside OpenClaw.
InfiniteTalk
Talking avatar video from audio
Grok Imagine
xAI image and video generation
Flux Kontext
Text-guided image editing
Z Image
Fast bilingual image generation
Topaz
AI image and video upscaling
Imagen 4
Google image generation
Seedream
Bytedance 4K image generation
Qwen 2 Image
Alibaba image generation and editing
Kling
Video generation with motion control and sound
Veo 3
Google cinematic video with native audio
Seedance
Budget video generation by Bytedance
Hailuo
MiniMax video with free daily quota
Wan
Open-source video and image generation
Runway
Creative video with camera control
Luma
Spatial-aware video generation
Suno
AI music generation from text
ElevenLabs
Text-to-speech and voice AI
GPT
OpenAI chat and responses API
Claude
Anthropic messages API
DeepSeek
Budget LLM with reasoning
Gemini
Google AI models, no GCP needed
Nano Banana
Google image generation with text rendering
Ideogram V3
Typography-focused image generation
Recraft
Vector art and image upscaling
Flux 2
BFL image generation, pro and flex
GPT Image
OpenAI image generation and editing
OpenClaw setup questions
Yes. OpenClaw supports custom OpenAI-compatible providers through models.providers. Configure RunAPI with the /v1 base URL, set api to openai-completions, and choose the provider-prefixed model reference in agents.defaults.model.primary.
No. Inside models.providers.runapi.models, use the provider-local ID such as gpt-5.5. Use the provider-prefixed reference runapi/gpt-5.5 when selecting the model in OpenClaw defaults or commands.
Store the key in RUNAPI_API_KEY and read it from the OpenClaw config. That keeps the credential out of version control and makes the same config usable across local shells, servers, and automation.
Yes. Keep models.mode set to merge and add RunAPI as one provider. Your existing providers remain available, and you can add fallbacks under agents.defaults.model.fallbacks when you want recovery behavior.
Yes. The same RUNAPI_API_KEY and /v1 endpoint you configured for chat also accept image generation requests. Specify a model like flux-kontext-pro or imagen-4, and OpenClaw can call it through the existing RunAPI provider — no GitHub skill or separate API key needed. For a full guide, see the OpenClaw image generation page.
Image, video, and music tasks are asynchronous. RunAPI returns a task ID on the first call. Your OpenClaw agent polls the status endpoint until the task completes, then receives the output URL. The RunAPI SDK handles polling automatically if you use it.
Use one RunAPI key inside OpenClaw.
Browse the model catalog, pick the model ID, and add it to your OpenClaw provider config.