Маршрутизация OpenClaw через Headroom Proxy для снижения счёта API
Headroom сжимает вывод инструментов OpenClaw локально (прокси 8787). onboard, OTEL, launchd.
Раскрытие: опциональная аренда Mac.
Архитектура
OpenClaw → Headroom http://127.0.0.1:8787 → API
| Mode | When | OpenClaw hook |
|---|---|---|
headroom proxy --port 8787 | Zero code change | Set ANTHROPIC_BASE_URL in ~/.openclaw/.env |
| ContextEngine plugin | Native OpenClaw path | Headroom providers/openclaw slice |
MCP headroom_compress | MCP-heavy flows | headroom mcp install |
headroom wrap | One-shot dev | Less ideal for 24/7 gateway |
Матрица
| Pattern | Hook | Savings band | Ops |
|---|---|---|---|
| Nightly launchd audit | Proxy + plist env | 70–92% on tool-heavy turns | Keep proxy alive with LaunchAgent |
| Interactive gateway chat | Proxy or plugin | 40–70% | Low gain on tiny prompts |
| MCP-only micro tools | MCP compress tool | 30–60% | When proxy blocked |
| Already on Ollama local | Skip Headroom | N/A | See Ollama OpenClaw guide |
| Need token accounting | Proxy + OTEL | Measure, don’t guess | headroom perf + spans |
Требования
- Шлюз OK · Python 3.10+
8 шагов
pip install "headroom-ai[proxy]"headroom proxy --port 8787headroom perfANTHROPIC_BASE_URL=http://127.0.0.1:8787- smoke agent
- плагин по желанию
- launchd
- OTEL
Ночной аудит
На больших логах 60–92% по публичным бенчмаркам.
MCP
Прокси + MCP, сверка через OTEL.
Ошибки
Отказ соединения: сначала прокси. Счёт без изменений: base URL.
Рекомендация
Тяжёлые tools → прокси.
FAQ
Does Headroom send my code to a third-party API?
No for the default local proxy—compression runs on your host; see limitations.
Will OpenClaw break if compression is too aggressive?
Headroom publishes benchmark accuracy tables; use CCR retrieve when the model needs full files. Smoke-test one real audit before automating.
What port should I standardize on?
8787 is the documented default for headroom proxy --port 8787.
How does this relate to Claude Code MCP Headroom?
Same project: headroom mcp install for MCP clients; OpenClaw users usually set provider base URL to the proxy.
Can I save ~80% on every request?
No—published ranges are 47–92% by workload. Log-heavy OpenClaw audits trend high; short chat trends low. Use headroom perf and OTEL.