In a chain of AI agents, one agent's mistake gets accepted by the next and builds up until it reaches the final answer. Cascade Guard checks every step, re-runs a failing step, and stops the order if it can't be fixed, so a wrong answer is never delivered silently.
This server is protected. Enter your key: an admin key (API_KEY), a reviewer key or a viewer key. It is kept only in this browser tab.
Faults are injected into the agents' outputs on purpose. Both sides get exactly the same faults.
Now the analyze and reason agents are a language model, and the guard is a second model call that checks each answer before the next agent uses it.
A real-world workflow on LangGraph: read the invoice, price it, approve it, write the summary. Every step is checked before the next one uses it. Paste your own invoice in the same layout, or use a sample.
Injected errors imitate real ones: a price with the decimal point moved, a wrong quantity, a dropped or duplicated line, a wrong tax rate, a flipped approval. Some mistakes are systematic and come back on a blind retry; with guided repair the agent is told exactly what was wrong (simulated for the rule agents, real for LLM agents).
Runs hundreds of random orders through the chain three ways and compares them.
Paste text from any agent. It flags empty output and known failure markers (CORRUPTED_OUTPUT, MISSING_DATA, INVALID_REASONING, TRUNCATED_OUTPUT).
Works for any agent, not just this demo: describe the task, paste what the agent was given and what it produced. JSON or plain text.
Every LLM run and LLM check is saved in a local database. Jobs the guard stopped, and checks that did not pass, wait here for a person to decide.
Any program can call the same API the dashboard uses. Interactive docs are at /docs.
The full evaluation, the same as cascade-guard eval: how often each agent is right, how many errors the checker catches and how often it wrongly rejects, and what the guard does end to end. Every rate comes with a 95% interval. Each seed is one independent repeat; results are pooled. Results are also saved in results/.
Sections 1 and 3 use rule-based agents, so they show how the chain's design lets errors through. Sections 2, 5 and 8 use your configured model (or the simulator); section 8 gives the measured error rates.