Prompt Caching

Caching is automatic — no parameter to set. Here is exactly what it costs on each tier.

#How it works

Prompt and response caching is fully automatic. There is no cache-control parameter to set — repeated and short queries are served efficiently by default, with nothing to configure on your side.

#Seeing cache hits

Every response surfaces cache activity in metadata.usage.cached_tokens, so you can see, per call, how much of the request was served from cache.

{
  "answer": "...",
  "metadata": {
    "usage": {
      "input_tokens": 12084,
      "output_tokens": 291,
      "total_tokens": 12375,
      "cached_tokens": 11820
    }
  }
}

Tip

Keep context stable to maximise cache hits — reuse the same birthDetails and a stable conversationId across follow-up turns instead of re-sending fresh values each time.

#Cost impact

Caching changes your bill in two distinct ways. Which one applies depends on whether the whole answer was reused, or only part of the input was.

#1. Answer-cache hit — flat $0.01, every tier

When you repeat an identical question for the same chart, the answer is served from the Vedika answer cache without calling the reasoning engine at all. That call bills a flat $0.01 on every tier, and the usage block reports zeros because no tokens were generated:

{
  "metadata": {
    "cost": { "costUsd": 0.01, "currency": "USD" },
    "usage": { "input_tokens": 0, "output_tokens": 0,
                "cached_tokens": 0, "total_tokens": 0 }
  }
}

#2. Reused input inside a live answer

When the engine runs and reuses part of your input, those cached tokens are priced per tier. The table below describes the current billable rate: some tiers discount reused input; others bill it at the normal rate and offer a latency benefit.

Tier	Cached input tokens	What caching buys you
Vedika Eco	Reduced rate — 37.5% of the fresh-input rate	Lower cost and lower latency
Vedika Standard	Same rate as fresh input	Latency only — no per-token discount
Vedika Standard 2.5	Same rate as fresh input	Latency only — no per-token discount
Vedika Swift	Same rate as fresh input	Latency only — already the fastest tier
Vedika Pro Ultra	Reduced rate — 10% of the fresh-input rate	Lower read cost and lower latency

Note

Cache pricing depends on the tier. Where a tier discounts cached input, you get a lower per-token rate; on other tiers, caching improves latency at the same input rate. Pro Ultra five-minute cache writes cost 1.25 times the fresh-input rate. Final deductions include all billable components and round to whole cents, with a $0.01 minimum for a billable answer, so a token discount may not change the final deduction. See your response billing metadata for the price and wallet deduction.

See Pricing for the full per-call rate table and Model Catalog for the per-tier capability grid.