Frequently asked questions
How much does trimming my prompt actually save?
Every token you remove from a prompt is removed from every single call that uses it. Multiply the tokens saved per call by your monthly call volume and the input price per million tokens. A 1,000-token cut on a prompt run a million times a month at $3 per million saves $3,000 monthly — the size of the prompt matters far more than most teams assume because it recurs on every request.
Does prompt compression affect output cost or quality?
Compression only touches the input side — output tokens and their price are unchanged. Trimming redundant instructions, verbose few-shot examples and duplicated context usually keeps quality intact, but cutting too aggressively can hurt accuracy. Combine trimming with prompt caching for stable prefixes so the remaining fixed context is billed at the discounted cache-read rate.