Asana says cache changes cut a browser agent's cost 76x
Summary
Asana says it reduced a browser-agent workflow's model cost by 76x (from $36.21 to $0.47 per run) and cut runtime from 22.5 to about 4 minutes by stabilizing page history to enable prompt caching and pruning screenshots in batches, rather than changing the underlying model.
Similar Articles
From $5.86 to $1.21 a day: what actually cut our AI agent bill (6 agents, real numbers)
A publishing company details how it cut daily AI agent API costs from $5.86 to $1.21 (a 79% reduction) by reducing agent wake-ups and switching from timer-based heartbeats to on-demand execution, while sharing lessons on caching, cost-per-result measurement, and moving agents off a laptop onto a server.
I benchmarked my browser agent against Browser Use on a live site (150 verified runs, same model). Sending page diffs instead of full re-renders cut token growth by 37%.
A developer benchmarks Rote, a memory manager for browser agents that sends page diffs instead of full re-renders, showing a 37% reduction in token growth compared to Browser Use, but with trade-offs on short tasks.
Cut my browser-agent cost 50x by NOT using an agent loop. Plan-then-execute + numbers.
Describes a technique to reduce LLM costs in browser agent tasks by using a single planning call followed by deterministic execution, achieving 50x cost reduction compared to standard agent loops.
Your Agentic Workflow's Cache Keepalive Costs 8x Too Much
A detailed measurement study across Anthropic, OpenAI, Gemini, and DeepSeek finds that the conventional 30-second prompt cache keepalive is 8x too frequent; a 4-minute interval is optimal, and only Anthropic's cache saves money at long idle gaps.
How Caching Saved Us Hundreds of Dollars in AI Costs Every Month
The article describes how building an intelligent caching gateway (Hawiyat Composer) saved significant AI API costs by eliminating repeated token waste through exact-match caching, semantic caching, model routing, and local routing.