CachePilot sits between your workloads and model providers to keep stable context cache-eligible, detect reuse-breaking drift, enforce execution policy, and prove expected versus actual reuse with auditable receipts.
BYOK · Content-free telemetry by default
X-CP-Mutations. Read the methodology →CachePilot does not promise to force opaque provider caches. It makes requests eligible for reuse, records the conditions, verifies the upstream result, and keeps policy attached to the execution.
Stable instructions, tools, and context should be paid for and processed once when the provider surface supports it.
A hit is only good when the reused state is still policy-correct, attributable, and safe for the current workload.
Lower input cost can follow valid reuse, but latency, drift, receipt completeness, and execution correctness may lead the decision.
The stable prompt, tool definitions, and context are present on every call, but one reordered field or missing breakpoint turns intended reuse into full execution. The provider accepts the request either way.
A cache-rate chart says performance changed, but not whether the request was eligible, which stable prefix moved, or whether the upstream provider actually reported cached tokens.
Prompts, params, budgets, and tool access change with no gate or receipt trail. Cost may move, but the earlier warning is lost reuse eligibility and an unexplained change in execution shape.
Swap the base URL, keep BYOK, and start in observe mode on OpenAI Responses or Anthropic Messages.
The first identical call is the warmup. The second lets CachePilot compare expected reuse with actual cached input tokens.
Enable repair and policy after the stable-prefix, reuse, latency, drift, receipt, and cost evidence supports it.
See whether the request had a stable, cache-eligible prefix before treating an upstream miss as a cost problem.
Compare the reuse CachePilot expected with the cached input tokens the provider actually reported on the repeated call.
Stabilize supported request prefixes, prompt cache keys, and Anthropic cache breakpoints without pretending an opaque provider hit can be forced.
Apply output budgets, model and tool policy, supported parameter repair, and observe-or-govern modes at the proxy boundary.
Pin a golden run and keep X-CP-* proof of the prefix, policy, mutations, budget, and cache-related behavior on each response.
Connect reuse, latency, tokens, and cost to a project and route without storing prompts or outputs by default.
Start with two identical calls in Free Observe, or run a dedicated 14-day design pilot that compares baseline and governed execution. Cost is included in the evidence, but it is not assumed to be the leading indicator.
The same checks we run in a teardown, self-serve and free.