Build consistent prefixes
Keep system instructions, tools and reusable examples stable. Avoid random ordering and unnecessary changes at the beginning of the prompt. Use supported cache keys or retention options only as documented by OpenAI.
Read the usage breakdown
Separate total input from cached input and compare actual cost. Cached tokens can still appear inside total input usage, so a dashboard must not treat them as removed. Inspect provider usage fields for every benchmark.
Local token estimate
This is an approximate comparison, not provider billing data.
Combine caching and reduction carefully
Varion keeps its proprietary engine implementation private. Commercial evaluation is based on measurable workload-specific outcomes, clear validation boundaries and customer-specific testing rather than disclosure of internal mechanisms. Use the dedicated Token Optimisation product area to evaluate whether the commercial result is suitable for your traffic; no universal performance percentage is promised.
Measurement checklist
- Choose a representative completed task, not an artificial one-line prompt.
- Record the selected model, provider input, cached input, output, retries and final result.
- Change one optimization mechanism at a time so the cause remains visible.
- Verify required identifiers, tool calls, code changes or business fields.
- Keep passthrough available when the reduced request does not pass.
Varion commercial evaluation
Varion keeps proprietary product implementation details private. Evaluate Token Optimisation on representative traffic and judge it by the measured commercial result. New verified users receive 100,000 processed input tokens and 50 local test runs.
Frequently asked questions
Are all OpenAI prompts cached?
No. Eligibility depends on current model and platform behavior. Consult the official prompt-caching documentation.
Does a cached token equal a removed token?
No. It is provider-reported cached input, not content removed from the request.