Know what caching really costs you.
Most tools assert an ROI you cannot check. This asserts nothing: it applies published provider cache multipliers to your own numbers, so you see where your input cost sits and what raising reuse is worth.
Your cache position
Enter your monthly context tokens and how often a cached prefix is reused. Every figure below comes from published provider multipliers, not from us.
What Surfil actually does about cost
Three things, each of them real today. None of them is a savings percentage we cannot back.
Protect the cache
Interception is byte-exact, so the prefix your provider caches still hashes the same and keeps hitting. This is the largest cost lever and Surfil never trades it away.
Prune only when it is safe
Cap rewrites redundant context ONLY on requests that declare no cache breakpoint. Rewriting a cached prefix would bust it and cost more than it saves, so Surfil refuses.
Measure, then sign
What you actually spent is measured on your own traffic and signed into a receipt you can verify offline. No percentage is asserted.
Stop estimating. Start measuring.
Install Surfil, keep working for a week, and Cap signs a receipt of what your agents actually cost - a measured number you can hand to finance and they can verify offline.