Get a provider API key
Create an API key from the AI provider account you already use.
Add the API keys you already have, choose a model and use it with OpenClaw without switching between multiple provider dashboards.
Manage your connected API keys
You only need an account and an API key from the provider you want to use.
Create an API key from the AI provider account you already use.
Select the provider, paste the API key and test the connection.
Select an available model and use it with OpenClaw, the Playground or a supported workflow.
Start with one provider and add more later when you need different models or capabilities.
Connect a provider key for reasoning, coding and general AI tasks.
Connect DeepSeek →Add a Qwen-compatible API key for Chinese and general business tasks.
Connect Qwen →Use your Gemini API key for general, document and multimodal-ready tasks.
Connect Gemini →Add your provider credentials for writing, analysis and document work.
Connect Claude →Connect a compatible API key for Chinese-language and longer document tasks.
Connect Kimi →Add your provider API details and access supported MiniMax models.
Connect MiniMax →Connect your own OpenAI API key and select supported models from the dashboard.
Connect OpenAI →Add your own Base URL and API key for a compatible provider that is not listed above.
Add Custom Provider →This platform does not issue provider API keys. You must obtain a key from the selected provider and remain responsible for that provider account, pricing and usage.
Select your provider, paste the API key and test the connection before saving it to your account.
Choose the AI service that issued your API key.
Paste the private key created inside your provider account.
Normally filled automatically. Custom compatible services may require their own API address.
Choose the model you want to use first. You can change it later.
Example dashboard form
Once a provider is connected, select it inside OpenClaw and choose an available model.
Add and test the provider API key inside your account dashboard.
In OpenClaw, open the model or API configuration area and select the provider you want to use.
Test a simple prompt before installing more Skills or building advanced workflows.
A Gateway Key gives OpenClaw or another supported application one connection point, while your original provider keys stay inside your private account settings.
Example account preview
The production backend must be completed and security-tested before real provider keys are collected.
Saved keys should only display a short masked identifier, never the full original value.
Test whether a provider key works before using it with OpenClaw or a workflow.
Prompt and response content logging is intended to stay disabled by default.
Users should be able to remove provider keys and revoke Gateway Keys from the dashboard.
Set request limits to reduce unexpected usage or accidental high-volume calls.
Users remain responsible for provider billing, terms, account access and model usage.
This page currently describes the planned account experience. Do not collect real API keys until server-side encryption, authentication, permission checks, rate limiting and security testing have been completed.
Simple answers about provider keys and the planned gateway.
Add your own API key, test the connection and use a supported model with OpenClaw from one simple dashboard.