Lever guide
What one lever does, its risk control, and how a policy enables it.
Lever 13
Cross-provider switch
A cheaper model from another provider you connected, only after a replay of your own requests holds quality. Not built.
Risk control
Switching would stay inside providers you connect. Disconnecting one removes it. Automatic rollback is not built.
It would sit with right-size, cascade, cache and trimming. Chat models first. Embeddings, speech, image and video are not in the code. Human review of samples would stay off unless you opt in. Voice recordings would be treated as sensitive personal data. If only one provider were connected, the move would stay on a cheaper model from that provider. Today the gateway prototype calls only OpenAI, and a replay stays inside one provider.
This lever can change the answer a user sees, so it stays off until a shadow test passes the threshold you set.
How a policy turns it on
Planned. Routing policies are designed to be per route. You would tag the route with X-Parezen-Route, then enable the lever on that route in the dashboard. Ignore is recorded. Nothing quality-affecting is enabled without a passed shadow test.
defaultHeaders: {
"X-Parezen-Route": "support-reply",
}