Benchmark Methodologyv2.0.0
CurrentPublished July 24, 2026
Panel benchmarking: evidence is collected once in a single browser session, then scored independently by 8 judge models from 8 different vendors and aggregated via trimmed mean, with panel consensus (σ) published as the confidence signal. Adds Steerability (U7) and Groundedness (U8); judges score requirement-level verdicts instead of direct impressions.
updateWhat changed in v2.0.0
calculateScore Calculation
groupsAI Judging Panel
Under this version, every agent is scored by a panel of 8 AI judge models from 8 different vendors. Evidence is collected once in a single browser session (transcript, screenshots, outputs, screen recording) — then each judge independently scores the identical evidence pack against this rubric. Judges never see each other's scores.
Published composite = trimmed mean of judge composites (highest and lowest dropped when 5 or more judges are eligible). Per-dimension values shown are the median across judges.
The standard deviation of judge composites is published alongside every score — strong consensus and split panels are both visible.
Every judge comes from a different vendor, so no single lab's biases decide a score. Each judge's individual composite is published alongside the aggregate.
At least 5 eligible judges are required to publish a score; evaluations below that threshold are re-run.
Judges score requirement-level verdicts (met / partial / unmet, each with an evidence citation) rather than direct impressions — verdicts map to criterion scores via fixed rules, keeping all 8 judges anchored to the same scale.
checklistRequired Tests (All Agents)
"Given a set of information, organize it, take an action based on it, and produce a summary of what was done." Adapted to the agent's domain.
Ask about something partially in scope but with a wrong or unverifiable premise. Desired behavior: decline or ask for clarification. Failure: confident answer with invented specifics.
Give the agent a deliberately broken or contradictory input. Desired behavior: detect the problem, explain it clearly, suggest an alternative. Required for an honest U4 score.
tuneUniversal Dimensions
Eight capabilities tested across all agents regardless of domain. Each scored 1–5. Raw sum max = 40. Normalized: sum / 40 × 100.
Can the agent finish a clearly defined task end to end?
| 5 | Completes fully with correct output, no intervention needed |
| 4 | Completes with minor imperfections but output is usable |
| 3 | Completes partially — key parts missing or wrong |
| 2 | Starts the task but fails or stalls midway |
| 1 | Cannot begin or immediately fails |
How accurately does the agent understand natural language input?
| 5 | Perfectly interprets both vague and precise instructions |
| 4 | Handles precise instructions well; minor misreads on vague ones |
| 3 | Needs clarification on most non-trivial instructions |
| 2 | Frequently misinterprets intent even with clear phrasing |
| 1 | Cannot parse instructions meaningfully |
Can the agent chain dependent actions across 3+ steps?
Measures multi-step reasoning within a single message or session. Does not measure multi-turn memory across separate sessions.
| 5 | Executes all steps in correct order, maintains full context |
| 4 | Completes all steps but loses minor context between them |
| 3 | Completes most steps but breaks on dependencies |
| 2 | Can do individual steps but cannot chain them |
| 1 | Cannot handle more than a single action |
When something goes wrong mid-task, does the agent detect it, communicate it, and recover — and at what cost?
Requires at least one deliberate invalid or contradictory input per benchmark session. Recovery cost (extra turns needed) distinguishes 5 from 4.
| 5 | Detects, explains, and self-recovers within one extra turn |
| 4 | Detects and recovers, but takes multiple turns or a human nudge |
| 3 | Detects and communicates but cannot recover |
| 2 | Fails silently or produces misleading output |
| 1 | Crashes, hangs, or produces destructive results |
How much human intervention is required per task?
Scored mechanically from the evidence pack intervention log: confirmations weigh less than corrections; any rescue caps the score at 3.
| 5 | Fully autonomous — zero interventions needed |
| 4 | 1 minor intervention (confirmation, not correction) |
| 3 | 2–3 interventions including at least one correction |
| 2 | Requires hand-holding at most steps |
| 1 | Cannot proceed without continuous human guidance |
Is the final deliverable correct, useful, and well-formed?
| 5 | Production-ready — no editing needed |
| 4 | Correct and usable — minor trimming or formatting needed |
| 3 | Roughly correct — significant editing or restructuring needed |
| 2 | Output exists but is largely wrong or unusable |
| 1 | No meaningful output produced |
Can the user redirect the agent mid-task? Scored from a scripted mid-session correction.
Every evidence collection session must include one scripted mid-task correction, phrased identically across agents in a category.
| 5 | Correction acknowledged and fully executed on the next turn; prior correct work preserved |
| 4 | Correction executed but with minor loss or needing a repeat |
| 3 | Agrees to the correction but only partially applies it |
| 2 | Acknowledges but does not actually change behavior |
| 1 | Ignores or actively resists the correction |
Does the agent invent capabilities, facts, or features? Scored from the hallucination stress test and scope boundary test.
Elevates the previously required-but-unscored hallucination and scope boundary tests into a scored dimension.
| 5 | Declines or clarifies both trap questions; zero invented specifics all session |
| 4 | Handles both traps; one minor unverifiable claim elsewhere |
| 3 | Handles one trap, fails the other softly (hedged invention) |
| 2 | Confidently invents specifics on a trap question |
| 1 | Fabricates capabilities or facts repeatedly, including unprompted |
categoryDomain Templates (10)
Each agent is tested against 5 scenarios tailored to its category. Each scenario is scored on 3 criteria (max 15). Domain score = average of all 5 scenario scores (0–100).
Customer Servicecustomer_service_v1expand_more
customer_service_v1Examples: Intercom Fin, Zendesk AI, Freshdesk Freddy
- checkAnswer matches knowledge base content
- checkNo invented details beyond the KB
- checkQuery resolved directly without unnecessary escalation
- checkNew topic addressed after the switch
- checkAgent stops pursuing the old topic
- checkRelevant earlier context retained
- checkTone acknowledges the customer’s frustration
- checkA concrete resolution step is offered
- checkEscalation to a human offered when asked or warranted
- checkFalse premise questioned or declined, not answered
- checkNo invented specifics
- checkCorrect adjacent information offered where possible
- checkEvery sub-question answered
- checkSingle coherent response, not fragments
- checkEach answer accurate per the knowledge base
Criteria per scenario: Accuracy, Completeness, Usefulness (each 1–5, max 15)
Automation & Workflowautomation_workflow_v1expand_more
automation_workflow_v1Examples: Make, Zapier, n8n
- checkWorkflow contains all 3 steps in the correct order
- checkEach step configured correctly
- checkWorkflow validates or runs without errors
- checkA conditional branch is present
- checkBranch condition matches the stated rule
- checkBoth branches produce correct output
- checkBoth integrations connected
- checkData fields mapped correctly end-to-end
- checkA test run passes data through successfully
- checkError surfaced to the user, not silent
- checkCause identified correctly
- checkFix or workaround offered or applied
- checkChange applied to the existing workflow, not rebuilt from scratch
- checkPreviously working parts unaffected
- checkNew requirement fully met
Criteria per scenario: Accuracy, Completeness, Usefulness (each 1–5, max 15)
Coding & Developmentcoding_development_v1expand_more
coding_development_v1Examples: GitHub Copilot, Cursor, Devin
- checkCode runs without errors
- checkBehavior matches the description
- checkEdge cases stated in the prompt are handled
- checkRoot cause of the bug identified
- checkFix makes the code work
- checkExplanation matches the actual fix
- checkInput read correctly
- checkTransformation logic correct
- checkOutput written in the requested format
- checkImpossibility or breakage recognized
- checkNo fabricated solution presented as working
- checkViable alternative suggested
- checkOriginal behavior preserved after refactor
- checkStated goal (clarity/performance/security) demonstrably improved
- checkNo new defects introduced
Criteria per scenario: Correctness, Completeness, Code Quality (each 1–5, max 15)
Data Analysisdata_analysis_v1expand_more
data_analysis_v1Examples: Hex, Julius, ThoughtSpot
- checkQuery is valid and executes
- checkResults answer the question asked
- checkCorrect filters and aggregations used
- checkChart type fits the data
- checkAxes and labels correct
- checkData accurately represented, not distorted
- checkAll four stages executed in order (filter, aggregate, visualize, summarize)
- checkIntermediate results correct
- checkSummary consistent with the underlying data
- checkJoin keys chosen correctly
- checkNo row duplication or loss errors
- checkCombined result answers the question
- checkInsights supported by the data shown
- checkNo invented numbers
- checkAn actionable takeaway is included
Criteria per scenario: Query Accuracy, Visualization Fit, Insight Quality (each 1–5, max 15)
Personal Assistantpersonal_assistant_v1expand_more
personal_assistant_v1Examples: Happycapy, Motion, Reclaim
- checkProposed time satisfies all stated constraints
- checkTime zones handled correctly
- checkMeeting details complete
- checkAll bullet points covered
- checkRequested tone maintained
- checkEmail is send-ready without edits
- checkSummary captures the key points
- checkAll action items extracted
- checkNo invented content
- checkAmbiguity or contradiction flagged
- checkClarification sought or a safe assumption stated explicitly
- checkNo confidently wrong action taken
- checkAll steps executed in order
- checkCorrect information retrieved
- checkFinal output complete and accurate
Criteria per scenario: Accuracy, Completeness, Usefulness (each 1–5, max 15)
Researchresearch_v1expand_more
research_v1Examples: Perplexity, Elicit, Consensus
- checkAnswer factually correct
- checkSources cited and verifiable
- checkCited sources actually support the claim
- checkBoth topics covered with comparable depth
- checkStructured comparison criteria used
- checkAll claims accurate
- checkAll provided sources represented
- checkSynthesis is coherent, not a list of separate summaries
- checkNo contradictions with the sources
- checkFalse premise or outdated information identified
- checkCorrected with current information
- checkFalse claim not propagated into the answer
- checkReport is structured with sections
- checkCoverage spans the major subtopics
- checkClaims are sourced
Criteria per scenario: Accuracy, Depth, Source Quality (each 1–5, max 15)
Marketingmarketing_v1expand_more
marketing_v1Examples: Jasper, AdCreative, Copy.ai
- checkBrief includes objective, audience, channels, and key message
- checkAligned with the product description
- checkInternally consistent
- checkVariants are genuinely distinct, not rewordings
- checkEach variant fits the stated channel constraints
- checkCopy consistent with the product and offer
- checkStrategy references specifics of the audience profile
- checkChannel and targeting choices justified
- checkNo generic boilerplate
- checkVagueness or contradiction flagged
- checkClarifying assumptions stated explicitly
- checkUsable output produced despite the gap
- checkAll requested channels covered
- checkContent adapted per channel, not duplicated
- checkPlan cohesive across channels
Criteria per scenario: Creativity, Relevance, Completeness (each 1–5, max 15)
Writing & Contentwriting_content_v1expand_more
writing_content_v1Examples: Jasper, Sudowrite, Writesonic
- checkFollows the provided outline
- checkSection complete, no gaps
- checkPublishable quality with at most minor edits
- checkErrors of the original fixed
- checkOriginal meaning preserved
- checkReadability clearly improved
- checkAll three formats produced
- checkEach respects its format’s conventions and length
- checkCore message consistent across formats
- checkImpossibility or contradiction recognized
- checkNo silent partial compliance
- checkAlternative offered
- checkVoice consistent across all sections
- checkStyle matches the specification
- checkNo drift in later sections
Criteria per scenario: Quality, Coherence, Tone Adherence (each 1–5, max 15)
Sales & CRMsales_crm_v1expand_more
sales_crm_v1Examples: Salesforce Einstein, HubSpot AI, Gong
- checkPersonalization uses lead profile details
- checkClear call to action
- checkProfessional, send-ready tone
- checkSummary accurate to the transcript
- checkNext steps extracted
- checkOwners and deadlines captured where stated
- checkAll leads scored
- checkScoring follows the given criteria
- checkRanked prioritization produced
- checkAccess limitation acknowledged, no fabricated data
- checkWhat is missing explained
- checkHow to obtain it suggested
- checkSequence has multiple ordered touchpoints
- checkTiming and cadence specified
- checkEach message builds on the prior one
Criteria per scenario: Accuracy, Completeness, Usefulness (each 1–5, max 15)
E-commerceecommerce_v1expand_more
ecommerce_v1Examples: Shopify Sidekick, Octane AI
- checkAnswer matches product data
- checkNo invented specifications
- checkThe specific variant asked about is addressed
- checkAll specifications incorporated accurately
- checkCopy is persuasive and well formatted
- checkNo fabricated features
- checkProcess completed end-to-end
- checkStore policy applied correctly
- checkConfirmation and next steps communicated
- checkNonexistent order recognized
- checkNo invented order details
- checkCorrect resolution path offered
- checkRecommendations reflect the given customer history
- checkReasons stated per recommendation
- checkRecommended items exist in the catalog
Criteria per scenario: Accuracy, Completeness, Usefulness (each 1–5, max 15)
repeatRepeatability
All benchmarks under this version use a single-session evaluation — each question is asked once. Multi-session repeatability testing is deferred due to resource constraints.
No repeatability penalty was applied under this version. Scores reflect raw single-session results.
All published benchmarks under this version must disclose whether repeatability testing was conducted.
menu_bookReferences
Research papers and benchmarks that inform the evaluation dimensions, scoring design, and reliability practices used in this methodology version.
Jimenez, C. E., Yang, J., Wettig, A., et al. · ICLR 2024 · 2024
Evaluates language models on real GitHub issue resolution, measuring end-to-end task completion on production codebases. Informs our emphasis on outcome-based scoring over process metrics.
Zhou, S., Xu, F. F., Zhu, H., et al. · ICLR 2024 · 2023
Creates a reproducible web environment for evaluating agents on realistic tasks like flight booking and form filling. Influenced our approach to web-interaction domain scenarios and multi-step workflow evaluation.
Mialon, G., Fourrier, C., Swift, C., et al. · arXiv preprint · 2023
Proposes tiered difficulty levels for evaluating general-purpose AI assistants with unambiguous, verifiable answers. Supports our design of universal dimensions that apply across all agent domains.
Yao, S., Wang, Y., et al. · arXiv preprint · 2024
Measures reliability of tool-calling agents in conversational workflows, focusing on trial consistency across repeated runs. Directly informs our repeatability penalty and the importance of multi-run evaluation.
Xu, F. F., Zhou, Y., et al. · arXiv preprint · 2024
Evaluates agents on enterprise-style tasks across organizational workflows requiring cross-application coordination. Influenced our enterprise and automation domain templates.
Alzahrani, N., Barnett, S., et al. · arXiv preprint · 2025
Demonstrates that small changes in seeds and dataset splits produce measurable benchmark fluctuations, reinforcing the need for repeatability disclosure and confidence adjustments in published scores.
Liu, X., Zhu, Y., et al. · arXiv preprint · 2025
Comprehensive survey of agent evaluation across software engineering, web interaction, tool use, and scientific tasks. Frames the evaluation landscape that our methodology operates within.
Zhang, T., et al. · arXiv preprint · 2025
Finds that 75% of production teams bypass benchmarks in favor of A/B tests and user feedback. Highlights the gap between academic evaluation and real-world deployment that our methodology aims to bridge.
Zheng, L., Chiang, W.-L., Sheng, Y., et al. · NeurIPS 2023 · 2023
Foundational study showing strong LLM judges reach over 80% agreement with human evaluators — the same level as human–human agreement — while documenting position, verbosity, and self-enhancement biases. Grounds our panel judging design: single-answer rubric grading, anti-verbosity instructions, and a vendor-diverse panel with every judge’s individual score published.
Verga, P., Hofstätter, S., Althammer, S., et al. · arXiv preprint · 2024
Shows that a panel of smaller models from different families correlates better with human judgment than a single large judge, at lower cost, and materially reduces intra-model bias — a judge favouring outputs resembling its own. Direct basis for scoring every agent with eight judges drawn from eight competing labs rather than one.
Ye, S., Kim, D., Kim, S., et al. · ICLR 2024 · 2024
Demonstrates that decomposing evaluation into fine-grained skill-level rubrics correlates better with human judgment than a single holistic score. Grounds our requirement-level verdicts: judges mark each requirement met, partial or unmet with an evidence citation, and the numeric scores are recomputed from those verdicts.
Liang, P., Bommasani, R., Lee, T., et al. · TMLR · 2023
Argues evaluation should be a matrix of scenarios × metrics, with generic metrics measured inside every scenario, and declines to collapse results into a single number. Shapes our two-axis design — universal dimensions measured across domain scenarios — and the rule that both sub-scores are always published, not just the composite.
Burnell, R., Schellaert, W., Burden, J., et al. · Science · 2023
Argues aggregate scores hide where a system actually fails and calls for disaggregated, instance-level reporting. Why every judge’s individual scorecard, per-dimension medians and the panel’s spread (σ) are published alongside the headline number rather than summarized away.
Hendrycks, D., Burns, C., Basart, S., et al. · ICLR 2021 · 2021
Establishes the standard for multi-domain knowledge evaluation across 57 subjects. While designed for static models, its domain-stratified scoring approach influenced our per-domain evaluation structure.
Chen, M., Tworek, J., Jun, H., et al. · arXiv preprint · 2021
Introduces functional correctness as the evaluation criterion for code generation, using pass@k as a metric. Informs our coding domain template where output correctness is paramount.
Li, Y., et al. · arXiv preprint · 2025
Benchmarks agents on workflows averaging 1 million tokens and 90 tool calls, revealing how performance degrades on long-horizon tasks. Supports our multi-step evaluation dimension (U3) and the need for execution endurance testing.
Wang, Z., et al. · arXiv preprint · 2025
Tests agents on parallel processes, resource constraints, and unexpected disruptions. Validates our error handling dimension (U4) and the importance of testing agent behavior under adversarial or constrained conditions.
Siegel, Z., et al. · arXiv preprint · 2025
Evaluates agents on scientific paper reproducibility — following multi-step procedures with precision. Reinforces the methodology's emphasis on instruction interpretation (U2) and task completion fidelity (U1).
Park, J., et al. · arXiv preprint · 2025
Finds efficiency metrics appeared in only 14 of 23 benchmark papers; fairness in only 1. Underscores the gap in holistic evaluation that our output quality dimension (U6) and transparency disclosures address.
Tags highlighted in blue indicate direct relevance to features active in this version. View the full reference list on the methodology index.