Native wire
OpenAI-compatible
Harness integration
OpenClaw with Tokaroo
Use Tokaroo as an OpenAI-compatible provider for OpenClaw agents and skills.
Integration contract
Keep OpenClaw's runtime. Replace the model connection.
Tokaroo does not host this harness. It receives the model request, selects a compatible route, handles fallback and metering, then returns the response in the harness's expected format.
Recommended model
Start with auto. Basic, Fast, Pro, and Max remain available for explicit workload requirements.
Family behavior
Optimized across compatible model families.
Profile status
The compatible provider path works, but full Tokaroo-only egress conformance is not yet promoted as guaranteed.
Configuration
Install, configure, and run the native harness.
Use OPENAI_API_KEY for the Tokaroo credential and OPENAI_BASE_URL for the gateway. The recipe below is the same compatibility path exercised by the Gwen runtime.
Install or verify the harness
npm install -g openclaw@2026.7.1Shell environment
export TOKAROO_API_KEY="tok_..."
export OPENAI_API_KEY="$TOKAROO_API_KEY"
export OPENAI_BASE_URL="https://api.tokaroo.com/v1"
export TOKAROO_HARNESS_REF="openclaw"OpenClaw provider configuration - ~/.openclaw/openclaw.json
{
"models": {
"mode": "replace",
"providers": {
"tokaroo": {
"baseUrl": "https://api.tokaroo.com/v1",
"apiKey": "${TOKAROO_API_KEY}",
"api": "openai-completions",
"headers": { "x-tokaroo-harness-ref": "openclaw" },
"models": [
{ "id": "basic", "name": "Tokaroo Basic", "contextWindow": 128000, "maxTokens": 8192 },
{ "id": "fast", "name": "Tokaroo Fast", "contextWindow": 128000, "maxTokens": 8192 },
{ "id": "auto", "name": "Tokaroo Auto", "contextWindow": 128000, "maxTokens": 8192 },
{ "id": "pro", "name": "Tokaroo Pro", "contextWindow": 128000, "maxTokens": 16384 },
{ "id": "max", "name": "Tokaroo Max", "contextWindow": 128000, "maxTokens": 16384 }
]
}
}
},
"agents": { "defaults": { "model": { "primary": "tokaroo/auto" } } }
}Start with a connection check
export TOKAROO_API_KEY="tok_..."
openclaw agent --local --message "Return exactly: Tokaroo connected"Required values
API key
OPENAI_API_KEY = your Tokaroo key
Base URL
OPENAI_BASE_URL = https://api.tokaroo.com/v1
Model
auto for the first run; switch to Basic, Fast, Pro, or Max only for a measured workload need
Profile
openclaw is a compatibility preference, never a hard model lock
The provider path works, but Tokaroo-only egress conformance remains conditional. Treat it as a tested integration path, not a hard routing guarantee.
Verify the wire
Test Tokaroo before starting a full harness run.
This direct request proves the key, protocol, model alias, and harness profile header independently of the harness process.
OpenAI-compatible verification request
curl https://api.tokaroo.com/v1/chat/completions \
-H "Authorization: Bearer $TOKAROO_API_KEY" \
-H "x-tokaroo-harness-ref: openclaw" \
-H "Content-Type: application/json" \
-d '{"model":"auto","messages":[{"role":"user","content":"Return exactly: Tokaroo connected"}]}'Expected response
A successful native response containing Tokaroo connected.
Usage fields
Record the trace ID, requested Tokaroo mode, input and output tokens, latency, and Tokaroo charge.
Harness capabilities
CLI, MCP, skills, agent tools.
Production checklist
Keep credentials and execution boundaries explicit.
The harness remains responsible for its own installation, updates, sandbox, filesystem, tools, and network policy.
Store the Tokaroo key in a secret manager or trusted runtime environment.
Use Auto first, then choose another Tokaroo mode only for a measured workload requirement.
Preserve the harness's native wire and tool event format.
Log Tokaroo trace, requested-mode, token, latency, and charge headers with the harness run identifier.
Set spend limits, retry 429 and 503 responses with backoff, and monitor balance before production rollout.
Route OpenClaw through one Tokaroo key.
Use Auto for the initial integration, then validate tool behavior, latency, usage, and output quality against your own workload.