Preset

Support bot · ticket_resolved · version 3

Cache

Exact-match response cache

Semantic cache: off in this sample. Turn it on for routes where similar questions can share one answer.

Support reply follows a cost-first policy.
A served response has to score at least 0.85 and finish inside 1,800 ms at p95.
Anything priced above $0.0200 a request is outside this policy.
Simple requests can move from anthropic/claude-sonnet-4.5 to anthropic/claude-haiku-4.5 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: anthropic/claude-haiku-4.5, anthropic/claude-sonnet-4.5.
Output is capped at 700 tokens, with reasoning effort low.
The route is synchronous, so it stays off batch prices.
Exact-match response cache is off for this route.
The near-duplicate (semantic) cache runs only on routes you list as safe for it.
Automation is manual. Nothing here applies on its own.

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.
The near-duplicate (semantic) cache is left out of this projection; it runs only on routes you list.