Home API Hub
Bring Your Own API Key

Connect Your AI Providers in One Place

Add the API keys you already have, choose a model and use it with OpenClaw without switching between multiple provider dashboards.

No platform credits required
Add multiple providers
Prompt logging off by default
🔑

My AI Providers

Manage your connected API keys

Secure
DeepSeek
sk-••••••••7F2A
Connected
Gemini
key-••••••••9B31
Connected
Qwen
sk-••••••••3C88
Connected
+ Add another provider
Your complete API key is not displayed after it has been saved.

Connect a provider in three steps

You only need an account and an API key from the provider you want to use.

1

Get a provider API key

Create an API key from the AI provider account you already use.

Examples: DeepSeek, Gemini, Qwen or another compatible provider.
2

Add it to your dashboard

Select the provider, paste the API key and test the connection.

The saved key is shown in masked form, such as sk-••••7F2A.
3

Choose a model and start

Select an available model and use it with OpenClaw, the Playground or a supported workflow.

You continue paying the provider directly according to its own pricing.

Connect the AI services you already use

Start with one provider and add more later when you need different models or capabilities.

DS
Available

DeepSeek

Connect a provider key for reasoning, coding and general AI tasks.

Connect DeepSeek →
QW
Available

Qwen

Add a Qwen-compatible API key for Chinese and general business tasks.

Connect Qwen →
GM
Available

Gemini

Use your Gemini API key for general, document and multimodal-ready tasks.

Connect Gemini →
CL
Available

Claude

Add your provider credentials for writing, analysis and document work.

Connect Claude →
KM
Available

Kimi

Connect a compatible API key for Chinese-language and longer document tasks.

Connect Kimi →
MM
Available

MiniMax

Add your provider API details and access supported MiniMax models.

Connect MiniMax →
OA
Available

OpenAI

Connect your own OpenAI API key and select supported models from the dashboard.

Connect OpenAI →
Flexible

Custom Compatible API

Add your own Base URL and API key for a compatible provider that is not listed above.

Add Custom Provider →
!

Provider account required

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.

Add a provider key without complicated setup

Select your provider, paste the API key and test the connection before saving it to your account.

1

Provider

Choose the AI service that issued your API key.

2

API Key

Paste the private key created inside your provider account.

3

Base URL

Normally filled automatically. Custom compatible services may require their own API address.

4

Default model

Choose the model you want to use first. You can change it later.

Add a Provider

Add AI Provider

Example dashboard form

Provider
DeepSeek
API Key
sk-••••••••••••••••7F2A
API Base URL
Provider API endpoint
Default Model
Select model
Priority
Primary
Test Connection Save Provider
i The final dashboard should never show the complete saved API key after setup.
OpenClaw connection

Use your connected provider with OpenClaw

Once a provider is connected, select it inside OpenClaw and choose an available model.

1

Connect your provider

Add and test the provider API key inside your account dashboard.

Provider: DeepSeek
Status: Connected
2

Open the model settings

In OpenClaw, open the model or API configuration area and select the provider you want to use.

Provider: OpenClaw Hub
Model: Select available model
3

Start a real task

Test a simple prompt before installing more Skills or building advanced workflows.

Prompt: Create a short launch plan
One simple connection

Use one Gateway Key for your connected providers

A Gateway Key gives OpenClaw or another supported application one connection point, while your original provider keys stay inside your private account settings.

  • Avoid placing every provider key in multiple applications.
  • Revoke or replace a Gateway Key without changing your original provider account.
  • Set request limits and restrict which models can be used.
  • View basic usage and error information from one dashboard.

Gateway Key

Example account preview

Key
oc_live_••••••••••••••••8K4P
Status Active
Models Selected models
Daily request limit 200
Prompt logging Off
The complete Gateway Key should only be displayed once when it is created. Users must store it securely.
Privacy and security

Simple controls for your keys and data

The production backend must be completed and security-tested before real provider keys are collected.

🔑

Masked keys

Saved keys should only display a short masked identifier, never the full original value.

Connection testing

Test whether a provider key works before using it with OpenClaw or a workflow.

Content logging off

Prompt and response content logging is intended to stay disabled by default.

×

Delete at any time

Users should be able to remove provider keys and revoke Gateway Keys from the dashboard.

Usage limits

Set request limits to reduce unexpected usage or accidental high-volume calls.

!

Provider responsibility

Users remain responsible for provider billing, terms, account access and model usage.

i

Development status

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.

Frequently asked questions

API Hub FAQ

Simple answers about provider keys and the planned gateway.

Create the key inside the account or developer console of the provider you want to use. This platform does not issue the original provider key.
No. Usage is subject to the provider account, balance, free allowance and pricing connected to your own API key.
A Provider Key is issued by a model provider. A Gateway Key is created by this platform and is intended to provide one connection point for providers already configured in your account.
The planned dashboard supports multiple provider records so users can choose different models for different tasks.
The planned custom provider option allows a compatible Base URL and API key. For security, the backend must only allow validated and approved destinations.
The current website code is the front-end interface. Key storage, connection testing, routing and usage tracking require the custom backend plugin before launch.

Connect one provider and start with a real task

Add your own API key, test the connection and use a supported model with OpenClaw from one simple dashboard.

滚动至顶部