Sample data. Not a customer bill.

Policy editor

Planned

Right-size, cascade, cache, batch, automation, YAML and history.

Prior auth · auth_decided · version 3

Cache

Exact-match is opt-in per route. Semantic cache is Planned.

Exact-match response cache

Semantic cache Planned

Auth summary follows a quality-first policy.
A served response has to score at least 0.90 and finish inside 1,400 ms at p95.
Anything priced above $0.0250 a request is outside this policy.
Simple requests can move from openai/gpt-4.1 to openai/gpt-4.1-mini only after a shadow test passes.
Cascade is off, so there is no cheap-first attempt.
If the chosen model fails, fallbacks run in order: openai/gpt-4.1-mini, openai/gpt-4.1.
Output is capped at 360 tokens and must be structured, with reasoning effort low.
The route is synchronous, so it stays off batch prices.
Exact-match response cache is off for this route.
Semantic cache is Planned and is not applied.
Automation is manual. Nothing here applies on its own.

12 sample requests on this route.

This sample has no cascade escalations. When one happens, its cost is included, not hidden.
Exact-match cache is off, so responses are not reused.
Semantic cache is Planned and is excluded.