Try to break an LLM call
Take a model down, cross a data boundary, or slip in a made-up answer, and see what the control plane does. Every call here runs on live AI and shows up in the call log.
Model failover
Every answer here runs on the same primary and fallback models our production chatbot uses. Turn on the outage and the primary model is treated as down, so you can watch the fallback take over with no error for the customer. Nothing is saved.
Answers come from the IrisAgent help center, the knowledge base of our demo account. The question is shared with the Data scoping tab.
Ask a question to see each model attempt, how long it took, and which model answered.
Data scoping
Multi-product and multi-tenant teams need each answer to come only from the data it is allowed to use. Pick a product and compare what retrieval finds across the whole knowledge base with what it finds once the call is scoped. The answer uses only the scoped articles. Nothing is saved.
Answers come from the IrisAgent help center, the knowledge base of our demo account. The question is shared with the Data scoping tab.
Run a comparison to see which articles each call can use. Articles that only an unscoped call would see are marked out of scope.
Grounding check
Before an answer reaches a customer, Iris Control checks it against the sources you approved. Every link must point at an approved source, and a judge model checks each claim against the source text. The sources below are from a fictional help center, so edit anything. Nothing is saved.
Check the made-up answer first: it invents a timeline, a credit, and a link. Then load the grounded answer and compare.
Call log
Every call on this page goes through one path, so every call is logged. Kept in this browser tab only.Run any tab above and its calls show up here.
Want to see this on your own LLM traffic?
We'll put Iris Control in front of one of your use cases and walk through failover, scoping, and grounding with your team.