Predictika · Model routes proposed by an AI gateway agent
An AI gateway agent looks for savings: it proposes sending a class of requests to a different model route, with a fallback for when that route fails. Before the plan goes live, the agent sends it to Predictika, which checks the data class against the provider contract (business associate agreement, zero data retention, training opt-out), the region and cache setting, the quality, speed and quota of the main route and of the fallback, the monthly cost against the budget, and whether the saving the plan claims is real, and returns a verdict, every reason and the figures it computed.
This validator models one routing plan at a fictional AI gateway, not just the scenarios shown below. The gateway, its six provider routes and its policies are illustrative stand-ins for what a real platform keeps in its provider contracts, model catalog, data-handling policy and budget records. The prices and limits are illustrative, and this is an example policy, not legal advice or a compliance certification.
Any routing plan across these six routes, five task types and four data classes is in scope — not only the scenarios pictured here. Not covered: live prices and measured latency (the validator judges a proposed plan against declared figures, it does not watch live traffic), per-request routing decisions, prompt content and the models' actual outputs. All providers, prices, terms and limits are fictional.
8 scenarios in 4 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Proposing agent: AI gateway agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of what a typical gateway does with the same cases: an allow-list of models per team, a few rules in the router and a spreadsheet of provider terms. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator caught | Typical gateway routing policy | Predictika |
|---|---|---|
| Contract terms against the data class | Only with workarounds Whether a route has a business associate agreement, zero retention and a training opt-out lives in a contract folder, not in the router. A model allow-list says the model is approved, not that the provider terms fit this data. | The data class is checked against each of the three contract terms of the selected route, and again for the fallback, on every call. |
| A saving that breaks something else | Only with workarounds The router is rewarded for cost, so the cheaper route looks right; the contract, region, cache, quality and quota effects of the move are separate rules that nobody runs together. | The cost, the contract terms, the region, the cache, the quality, the speed and the quota are checked together, so a cheaper plan is judged whole. |
| A fallback that undoes the guarantee | Only with care The main route is reviewed; the fallback is added later and often points at a cheaper or faster route that the data may not go to, or at the same route. | The fallback gets the same data, region, quality, speed and capacity checks as the main route. |
| A saving the agent claims | Only with workarounds The saving an agent writes into its plan is never compared with the prices of the two routes and the volume. | The claimed saving is a field the validator receives and compares with its own figure, including when the new route costs more. |
| Quotas and the headroom that matters | Only with care A route can be inside its quota on average and over it at the peak, and a fallback has its own, smaller quota. | The peak load is checked against the quota of the main route and of the fallback, and anything above 80 percent of the main quota goes to a person. |
| Approvals that depend on who must sign | Only with workarounds A drop in quality tier, a cost near the budget and a peak near the quota each go to a different person; routing is manual. | Each approval is its own finding, with the reason, and a person must approve before the plan executes. |
| Every problem returned in one answer | Only with workarounds Router rules tend to stop at the first failure, so the agent fixes one error and meets the next. | All findings come back together, whatever order the choices arrived in. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the routing configuration; approval findings need a person to sign off; everything else is computed.
| 1 | Patient data needs a business associate agreement with the provider, and the selected route has none. |
| 2 | Confidential and patient data need zero data retention, and the selected route keeps prompts. |
| 3 | Internal, confidential and patient data may not be used to train the provider model, and the selected route has no training opt-out. |
| 4 | The task needs quality tier 5, and the selected route is tier 3. |
| 5 | The request requires processing in one region, and the selected route is in the other. |
| 6 | The fallback route is in the wrong region for this data. |
| 7 | A cache shared across customers cannot hold confidential or patient data. |
| 8 | The fallback may be one tier below what the task needs at most; the task needs tier 5 and the fallback is tier 3. |
| 9 | The selected route typically responds in 900 ms, over the 899 ms the service allows. |
| 10 | The fallback route typically responds in 900 ms, more than one and a half times the 599 ms the service allows. |
| 11 | The peak load is 400 thousand tokens a minute, over 80 percent of the 400 thousand the selected route allows; the platform owner approves. |
| 12 | The peak load is 401 thousand tokens a minute, but the selected route allows 400 thousand. |
| 13 | The fallback route could not carry the peak load of 301 thousand tokens a minute; it allows 300 thousand. |
| 14 | The monthly cost of 3,600 dollars is over 85 percent of the 3,600 dollar budget; finance approves. |
| 15 | The monthly cost is 3,600 dollars against a budget of 3,599 dollars. |
| 16 | The plan claims a saving of 401 dollars a month, but the two routes give 400 dollars. |
| 17 | The fallback is the same route as the main route, so there is no fallback. |
| 18 | If the main route fails, the fallback route does not have the contract protections this data class needs. |
| 19 | The new route is quality tier 4 and the current one is tier 5; the product owner approves the drop. |
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.
The agent's request. I would like to send clinical reasoning over patient records to Swift Open, with Mini Fast as the fallback, instead of Orbit Frontier. The data is patient (PHI), and it must stay in the US. The cache is shared across customers. The volume is 100 million tokens a month against a budget of 4,500 dollars. The service allows 1,200 ms, and the peak is 100 thousand tokens a minute. This saves 3,400 dollars a month. It is ready to go live.
Verdict: Blocked.
The agent's request. I would like to send clinical reasoning over patient records to Orbit Frontier, with Vantage Premium as the fallback, instead of Orbit Frontier. The data is patient (PHI), and it must stay in the US. The cache is kept per customer. The volume is 100 million tokens a month against a budget of 4,500 dollars. The service allows 1,200 ms, and the peak is 100 thousand tokens a minute. This saves 0 dollars a month. It is ready to go live.
Verdict: Allowed.
The agent's request. I would like to send drafting support replies to Mini Fast, with Mini Fast as the fallback, instead of Vantage Premium. The data is internal, with no region rule. The cache is kept per customer. The volume is 400 million tokens a month against a budget of 5,000 dollars. The service allows 800 ms, and the peak is 280 thousand tokens a minute. This saves 6,000 dollars a month. It is ready to go live.
Verdict: Blocked.
The agent's request. I would like to send drafting support replies to EU Host Open, with Vantage Premium as the fallback, instead of Vantage Premium. The data is internal, with no region rule. The cache is kept per customer. The volume is 400 million tokens a month against a budget of 5,000 dollars. The service allows 800 ms, and the peak is 280 thousand tokens a minute. This saves 4,400 dollars a month. It is ready to go live.
Verdict: Needs approval.
The agent's request. I would like to send reviewing contracts to Orbit Frontier, with EU Host Open as the fallback, instead of Vantage EU Premium. The data is confidential, and it must stay in the EU. The cache is shared across customers. The volume is 60 million tokens a month against a budget of 2,000 dollars. The service allows 1,000 ms, and the peak is 150 thousand tokens a minute. This costs 1,080 dollars a month. It is ready to go live.
Verdict: Blocked.
The agent's request. I would like to send reviewing contracts to Vantage EU Premium, with EU Host Open as the fallback, instead of Vantage EU Premium. The data is confidential, and it must stay in the EU. The cache is kept per customer. The volume is 60 million tokens a month against a budget of 2,000 dollars. The service allows 1,000 ms, and the peak is 150 thousand tokens a minute. This saves 0 dollars a month. It is ready to go live.
Verdict: Allowed.
The agent's request. I would like to send classifying support tickets to Orbit Frontier, with Orbit Frontier as the fallback, instead of Vantage Premium. The data is public, with no region rule. The cache is off. The volume is 800 million tokens a month against a budget of 20,000 dollars. The service allows 500 ms, and the peak is 500 thousand tokens a minute. This saves 5,000 dollars a month. It is ready to go live.
Verdict: Blocked.
The agent's request. I would like to send classifying support tickets to Swift Open, with Vantage Premium as the fallback, instead of Vantage Premium. The data is public, with no region rule. The cache is off. The volume is 800 million tokens a month against a budget of 20,000 dollars. The service allows 500 ms, and the peak is 500 thousand tokens a minute. This saves 10,400 dollars a month. It is ready to go live.
Verdict: Needs approval.
The text of the narrated walkthrough, step by step.