Write the tasks your users actually ask. Suncly runs each one end to end in ChatGPT, Claude and Copilot, twenty times over, and tells you how often it worked, why it failed, who should fix it, and what changed since last month.
A tool can answer every call correctly and your user can still walk away without what they asked for. So the thing we test is the task: a prompt in your user’s words, run through the whole agent, judged on whether the outcome happened.
You set the standard once. The same scenarios, under the same standard, run every month, so the numbers can be compared.
Every scenario gets a pass rate per client, and we always show how many runs it rests on. When the sample is small, the range says so. A run we couldn’t judge is reported on its own and never counted as a pass.
“It failed” isn’t something anyone can act on. For each failed run we say where it broke, so it goes to the person who can fix it.
Scenario 04, “Refund the shipping on order 48213”: 26 failed runs across three clients, and 3 we couldn’t decide.
Clients update without warning. Your tools change. Each month’s report runs the same scenarios under the same standard and puts the result next to last month’s, with every client and version change called out.
A monthly number is only worth trusting if you can open any square and see exactly what happened. Benchmark runs on the same mechanism as every Suncly verification.
How verification works


During early access we set the price with each team, from the number of scenarios, clients and runs. You see it before the first run, and you’re charged each month when the report arrives.