The failures that pass every health check
Five modes across two axes. The severe ones return HTTP 200 and corrupt state.
Case studyYour base URL
api.metriqual.com/v1
One request, mid-outage
Conversation history carried across. Your user never saw an error.
Every model call you make runs through providers you do not control. Metriqual holds the keys, picks the model, replays the request when one stops answering, and prices every call against the key that made it.
Every call comes back priced. The dashboard ranks the models your key actually used, so the cheaper one that still answers is a change you can make on purpose.
When a provider stops answering, the request is replayed against the next one in the chain with its history intact.
The same key reaches all of them.
Logged against the key that made the call.
Change the base URL and the key. The rest of your call stays where it is.
https://api.openai.com/v1
https://api.metriqual.com/v1/chat/completions
-H "Authorization: Bearer mql_your_key"
Metriqual holds the provider keys. Your code never sees them, and never changes when the routing does.
Streamed chat with tool calls, voice turns with per-stage latency, and image generation, all through one endpoint. Failover covers all three.
What's our refund window, and does it apply to annual plans too?
Refunds are available within 14 days of purchase. Annual plans are included, prorated for the unused months rather than refunded in full
Four steps from your current provider call to a routed one. The migration is the first line of the first step.
Read the docsSwap the base URL and the key in the SDK you already use. Nothing else in the call changes.
It holds the provider keys and routes each call by the rules you set, so your code never carries a provider name.
When a provider stops answering, the request goes to the next one in the chain carrying its conversation history.
Model, key and spend are attached to each request, and a key cannot spend past the ceiling you set.
744 of 750 events preserved on reroute. A stateless gateway preserved none of them.
Five modes across two axes. The severe ones return HTTP 200 and corrupt state.