What's this about?
A 144-run study tested one demo-catalog task. Model switching plus workflow changes produced the headline 76× saving versus the original setup; within GPT-6.1 Sol, caching/screenshot policy reduced cost from $1.97 to $0.47. The study used three repeats per configuration.
What exactly is prompt caching?
Reusing an unchanged prefix of previously processed input, so repeated context can cost less. Editing old history too often breaks reuse.
What's the community saying / why does it matter?
No independent discussion collected. The vendor-hosted customer account supports a workflow lesson, not a universal 76× model advantage.