Two rates, not one score
How often "done" is true, and how often "I couldn't" is true, by task family, with confidence intervals.
What we offer
An independent evaluation of how often an AI agent's completion claims are true, on a private test suite. In development; design partners first.
In development. Design partners get the first evaluations.
How often "done" is true, and how often "I couldn't" is true, by task family, with confidence intervals.
A test suite the agent cannot have trained on, run by us, so the score measures the skill and not the training data.
The method is published, every major model goes on a free leaderboard, and payment never changes a score.
When an AI agent reports that a task is done, Inoku Verified™ measures how often that report is true. It also measures the opposite case: when the agent says a task could not be done, how often that is true.
An agent gets a result on two questions.
Both numbers are broken down by task family (coding, operations, data and so on, agreed with you) and reported with confidence intervals. A single headline score hides too much.
The problem is not marginal. In one 2026 study of coding agents that reported their own status, false success made up 75.8% of all failures (Advani, 2026). The agents did not crash. They said “done”.
Two things undermine most published agent scores.
A lab can’t credibly grade itself. The most common check today is an LLM judge reading the agent’s own transcript. Measured against ground truth, the best such judge reached an AUROC of 0.65 on τ²-bench and 0.54 on AppWorld (Advani, 2026). A judge run by the organisation that built the agent adds a conflict of interest on top. See Inoku vs LLM-as-judge.
Public tasks leak into training data. Once a benchmark is public, its tasks end up in the data future models learn from, and the score stops measuring the skill it was meant to measure. This is benchmark contamination. ARC Prize deals with it by keeping evaluation sets that are never published and running the tests itself (ARC Prize, 2024). Inoku Verified™ follows the same practice: a private suite the agent cannot have trained on, with held-out tasks that stay private.
There is a third reason. Agents can change their own records. In one study, most of the agent harnesses tested let the agent delete or rewrite its own traces, and the authors recommend keeping logs outside the agent’s control (Qin et al., 2026). An evaluation that relies on what the agent says about itself measures the agent’s writing, not its work.
These are commitments, written in the future tense because none of them is true yet.
Inoku Verified™ is in development. The first evaluations go to design partners, at no cost during the programme. Model builders who want a confidential run can read about private evaluations. Larger organisations pay once the programme ends; see pricing. For the thinking behind the approach, start with how to verify what an AI agent actually did.
Evidence
Every factual claim on this page links to one of these. Numbers in brackets refer to this list.
Questions
We're looking for a small group of teams that build or run AI agents on real systems.
Become a design partner