Preset

Code review · review_posted · 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.

Code review agent follows a latency-first policy.
A served response has to score at least 0.84 and finish inside 450 ms at p95.
Anything priced above $0.0150 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 600 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.
Parezen only suggests. A person still chooses Enable or Ignore.

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.