The job here is not just to collect keys. It is to match a provider key to a model you can actually use in OpenClaw today, then verify that the auth path is healthy before you build on it.
Quick answer
List or scan the candidate models first, then attach the provider key in the model config flow, and finish with openclaw models status --check.
Command line steps
1. Find the model candidates first
This prevents you from wiring a provider into OpenClaw before you even know what you want from it.
BASH
$openclaw models list --all
openclaw models scan --no-probe --max-candidates 12
2. Attach the provider credential
Use the model section so the provider and model choices stay in one flow.
BASH
$openclaw configure --section model
3. Verify the credential path
A provider key only counts if the status view agrees with you.
BASH
$openclaw models status --check
openclaw models status --probe
What to check if it still fails
- If status warns about missing auth, the key was not saved where OpenClaw expects it.
- If you can see the model in the catalog but cannot select it, review the allowlist and aliases in the model config flow.
- If the free tier is unstable, use it for testing only and move to a more reliable default later.