All clients
OpenClaw
Personal agent with a non-interactive onboarding flow.
Base URL
https://api.bf16.ai/v1Protocol
openai-completionsWho this is for
People running a personal agent whose permissions, not the model, decide what it may do.
Commands show $BF16_API_KEY. Sign in to fill in your own key automatically.
- 1
Export your key
When signed in, your own API key is filled in automatically below.
export BF16_API_KEY=sk-bf16-v1-... - 2
Onboard against bf16
openclaw onboard --non-interactive --accept-risk \ --auth-choice custom-api-key \ --custom-provider-id bf16 \ --custom-compatibility openai \ --custom-base-url https://api.bf16.ai/v1 \ --custom-api-key "$BF16_API_KEY" \ --custom-model-id deepseek/deepseek-v4.1-flash-uncensored \ --skip-health
How to know it worked
- OpenClaw reports the custom provider as connected.
- curl https://api.bf16.ai/v1/models -H "Authorization: Bearer $BF16_API_KEY"
Common errors
Symptom
Onboarding stops at the provider step.
Cause
The custom base URL is missing its /v1 suffix.
Fix
Use https://api.bf16.ai/v1.