Just fixing the cache

·2026.04.15 23:21

Key point

Fixing the cache settings dropped OpenClaw's per-call cost from 13 cents to 2 cents.

Details

Putting a proxy in front of OpenClaw and logging all API calls immediately revealed the cause of the cost spike.

Cache misses were occurring on most calls, caused by incorrect configuration.
Unnecessary tasks added long ago were also still running.
Some tasks also had room to be run on a cheaper model.

The model and prompts weren't changed at all; simply fixing the cache settings brought the average per-call cost down from 13 cents to 2 cents.

The proxy built in the process was released as a free tool so others could use it too.

llm anthropic openclaw caching proxy api-cost devtools

Read originalShare on Threads

This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.

Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.