Set a spending cap. ClawCap enforces it and picks the cheapest model that works.
Get StartedBut you do. And when something goes wrong at 3 AM, you need a safety net — not a laptop.
Install once. Protect everything from anywhere.
One command: npm install -g clawcap
clawcap init — wizard for API keys, caps, and Telegram.
clawcap start — proxy is live. Point your agent at localhost:5858
ClawCap enforces caps 24/7. Check spend from your phone via Telegram /status
The core is simple: set a cap and it's enforced. Everything else is optional protection.
Set daily and monthly limits. When you hit them, requests get blocked with a clean 429. Not throttled. Blocked.
Catches agents stuck in loops — repeated payloads, error floods, rapid-fire requests. Auto-pauses and alerts you.
Detects idle keep-alive calls and routes them to a cheap model. Blocks heartbeats during sleep hours.
Kill or resume agents from Telegram. Get proactive alerts at 80% and 95% of your cap. No laptop required.
Anthropic, OpenAI, Gemini, DeepSeek, Mistral, xAI, Groq, MiniMax, Moonshot. Routes by model name.
Telegram bot, CLI commands, HTTP API — control your agents from whatever channel you prefer.
Start free with core protection. Upgrade when you need alerts, wallets, and team features.
Everything you need to know.
Yes. ClawCap is a transparent proxy. Any tool that can point to a custom API base URL works — OpenClaw, LangChain, AutoGPT, custom scripts, anything that calls Anthropic or OpenAI-compatible APIs.
Under 5ms. ClawCap runs on localhost and checks are in-memory / SQLite. The bottleneck is always the upstream LLM API, not the proxy.
ClawCap reads token counts from API responses and multiplies by the model's known pricing. Costs are stored in a local SQLite database. No data is sent anywhere.
Keys are stored in your local .env file and never leave your machine. ClawCap runs entirely on your infrastructure. No telemetry, no external calls, no phone-home.
ClawCap returns a 429 status with a clear JSON error message explaining the cap was reached. Your agent gets a clean signal to stop, not a mysterious failure.
No. Telegram is optional. You can control everything via the CLI with clawcap status, clawcap kill, and clawcap resume.
Yes. ClawCap includes a Dockerfile for containerized deployment. Build with docker build -t clawcap . and run with docker run -p 5858:5858 --env-file .env clawcap.
Sign up for a plan, install the CLI with npm install -g clawcap, then run clawcap init for interactive setup. You'll be protected in under 2 minutes.
Set your cap. Point your agent at ClawCap. From that point on, your agents can't burn more than you allow.
Get Started