Assistant (default)
Chat-based assistant with smart escalation
routing_mode: "assistant"Get Started
Setup Wizard
Pick your mode. Set your budget. Get your config. Run.
Steps4
Time3 min
OutputCopyable JSON
1
Choose your mode
How will you use Toolklaw?
Reference
Common configurations
Pre-built configs for common use cases.
Operator (budget)
Robot control, ultra-cheap, no premium
routing_mode: "builder"Embodied (safety)
Robot with safety gates and structured output
routing_mode: "embodied"Help
Integrate with OpenClaw
How to plug this config into your gateway.
1. Install Toolklaw Client
pip install toolklaw-client2. Add Config to gateway.yaml
providers:
toolklaw:
type: "llm"
config: |
provider: toolklaw
model: tk_claw
routing_mode: assistant
# ... paste your config here3. Set Your API Key
export TOOLKLAW_KEY="tkc_live_..."4. Start Your Gateway
python3 -m openclaw.gateway --config gateway.yaml5. Test It
curl -X POST http://localhost:8000/message \
-d '{"text": "Hello"}' \
-H "Content-Type: application/json"Troubleshooting
Common issues
How to fix things if they don't work.
Invalid API key error
Check that your TOOLKLAW_KEY is set and valid. Get a new one from your dashboard.
Routing not working
Make sure your config has routing_mode: "assistant" (not a typo). Test with a simple prompt first.
Budget cap hit too early
Increase your max_per_turn_cents in the config. Some prompts need more. Check your usage in the dashboard.
BYO premium not escalating
Add your GPT key to dashboard Settings → Providers. Check that byo_enabled: true in your config.
Timeout errors
tk_claw usually responds in <500ms. If you're hitting timeouts, check your network. File an issue in Discord.
Still stuck?
Join our Discord. Operators help operators. Or email support@toolklaw.com.
Ready to run cheap?
Your config is ready. Get an API key and start building.