Drop in a real conversation and this tool does the math your bill would do: how many input tokens PromptCrunch forwards, how many it strips, and what you pocket every month. Identical responses, a fraction of the input cost.
Monthly math: we assume a conversation like the one you pasted runs [conversations/day] times a day, each turn re-sending its growing history, approximated as (turns ÷ 2) × total tokens per conversation. The flat subscription ($29/mo Pro, $199/mo Agency) is the only cost on top.
Numbers look right? Point it at your real traffic, free.
Good, keep it. Cached requests pass through untouched, so PromptCrunch is never worse than sending direct, and it crushes the input bill on every request that isn't a cache hit. See how caching and PromptCrunch stack.
These are the live proxy's real thresholds, the same math your production traffic runs through. Read them and check our work.
~1,500 tokens each.12,000 tokens is forwarded untouched, so you're never charged more than going direct. Compression kicks in exactly where the money is: long, growing conversations.4 messages always go through verbatim, so the model keeps full fidelity on what was just said.{ or [), base64 runs, images, tool calls, and tool results in older history pass through verbatim. Never compressed, never touched.0.4 ratio: forwarded = protected + 0.4 × compressible + the last 4 messages.Two lines of config point your SDK at PromptCrunch. The free tier hands you $5 of credit and 100 requests a day, no card, so your real conversations prove the number for themselves.