IA / Automatisation 4 juin 2026

Router OpenClaw via le proxy Headroom pour réduire la facture API

VpsGona Équipe 4 juin 2026 ~14 min
OpenClaw Headroom

Headroom compresse localement les sorties outils OpenClaw (proxy 8787). onboard, OTEL, launchd.

Divulgation : location Mac optionnelle.

Architecture

OpenClaw → Headroom http://127.0.0.1:8787 → API
ModeWhenOpenClaw hook
headroom proxy --port 8787Zero code changeSet ANTHROPIC_BASE_URL in ~/.openclaw/.env
ContextEngine pluginNative OpenClaw pathHeadroom providers/openclaw slice
MCP headroom_compressMCP-heavy flowsheadroom mcp install
headroom wrapOne-shot devLess ideal for 24/7 gateway

Matrice

PatternHookSavings bandOps
Nightly launchd auditProxy + plist env70–92% on tool-heavy turnsKeep proxy alive with LaunchAgent
Interactive gateway chatProxy or plugin40–70%Low gain on tiny prompts
MCP-only micro toolsMCP compress tool30–60%When proxy blocked
Already on Ollama localSkip HeadroomN/ASee Ollama OpenClaw guide
Need token accountingProxy + OTELMeasure, don’t guessheadroom perf + spans

Prérequis

  • Passerelle OK · Python 3.10+

8 étapes

  1. pip install "headroom-ai[proxy]"
  2. headroom proxy --port 8787
  3. headroom perf
  4. ANTHROPIC_BASE_URL=http://127.0.0.1:8787 · restart gateway
  5. smoke agent
  6. plugin optionnel
  7. launchd
  8. OTEL

Audit nocturne

Fortes économies sur logs/diffs (47–92 % publiés).

MCP

Proxy + MCP, mesurer avec OTEL.

Dépannage

Connexion refusée : démarrer Headroom d’abord. Facture plate : vérifier base URL.

Outils lourds → proxy obligatoire.

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.

Déployer le proxy

8787, base URL, mesure perf + OTEL.