System 06

Model Routing Gateway

Type a request and see which size of model it gets sent to, why, and what that choice costs against the alternatives.

What it does

Type anything you would ask an AI assistant. The page measures the request before any model sees it: what kind of task it is, how long the answer needs to be, whether it involves maths or code, and how vague the wording is. Each of those adds to a single score, and you can see exactly how much each one contributed.

That score picks one of three model sizes. The page then really calls that model and prices the call, alongside what the cheapest and the most expensive model would have charged for the same request, so the saving or the overspend is a number rather than a claim.

It also shows the rules that can overrule the score: a customer who pays for the big model regardless, an overnight batch account capped at the cheap one, and endpoints pinned to a fixed size. Then it replays your request twice more, once against a deliberately tiny spending cap so you can watch it get downgraded and then refused, and once with the chosen model returning an error so you can watch it fall back to another one.

Try it

translate hi to FrenchExplain why our webhook retries are double charging customers, and comClassify this ticket as billing, bug or feature request: my invoice waWrite a python function that verifies an HMAC-SHA256 signature header