Preview the request behavior and tradeoffs here. A demonstration does not enable a transformation on your API traffic.
Eight available techniques
Choose deliberately
Every optional technique starts off. Enable account controls for eligible requests, or choose a variant-specific selection in an experiment. Savings remain unmeasured without a control comparison.
Pruning can remove context. Concise instructions can change an answer. Model routing changes the serving model. Preview the change and evaluate it on your workload before enabling it.
Response caching is explicit
Exact caching stores eligible response text per user for reuse within 15 minutes, up to 100 entries of 256 KiB each. It never stores prompt text. Only temperature-zero, non-streaming plain-text requests without tools qualify. Disabling the account setting clears existing entries; an active experiment explicitly enabling caching can still create new entries. Expired entries are cleaned during writes.