Skip to main content
If you already have agent execution results from other sources, you can use our standardized evaluation service to assess performance.

Overview

Use Cases:
  • You have results from custom agent implementations
  • You want to use standardized evaluation metrics
  • You’re preparing to submit to the Leaderboard
What We Provide:
  • Standardized evaluation pipelines for each benchmark
  • Consistent scoring metrics
  • Detailed performance reports

Universal Data Requirements

Directory Structure

All benchmarks require this basic structure:

Universal result.json Format

All benchmarks require these base fields:
Field Descriptions:
  • task_id: Unique task identifier matching the benchmark
  • task: Human-readable task description
  • answer: Agent’s final response or answer
  • model_id: LLM model used (e.g., “gpt-4o”, “claude-3.5”)
  • browser_id: Browser configuration (e.g., “Chrome-Local”)
  • metrics: Optional performance metrics

Benchmark-Specific Requirements

LexBench-Browser

Evaluation Method: Visual assessment using screenshot sequences
Scoring: 0-100 scale, default threshold: 60

Additional Requirements

Required: Screenshot files in trajectory/ directory
Format: PNG or JPG images
Naming: Sequential numbering (e.g., 0.png, 1.png, …)

Example result.json

Required Directory Structure

Evaluation Command

Note: Place your results in the standard experiments directory:

Online-Mind2Web

Evaluation Method: WebJudge multi-round evaluation
Scoring: 3-point scale, default threshold: 3

Additional Requirements

Required: action_history field in result.json
Required: Screenshot files in trajectory/ directory
Format: Action history as string array

Example result.json

Required Directory Structure

Evaluation Command

Note: Place your results in:

BrowseComp

Evaluation Method: Text answer accuracy comparison
Scoring: Binary (correct/incorrect)

Additional Requirements

Not Required: Screenshots (text-only evaluation)
Required: Complete answer field with full response

Example result.json

Minimal Directory Structure

Evaluation Command

Note: Place your results in:

Evaluation Process

Step 1: Prepare Your Data

  1. Organize Results: Structure your data according to the requirements above
  2. Place in Standard Location: Copy to the appropriate experiments directory
  3. Verify Format: Ensure all required fields are present

Step 2: Run Evaluation

Execute the evaluation command:
Optional Parameters:
  • --model: Evaluation LLM (overrides eval.model from config.yaml)
  • --score-threshold: Custom success threshold
  • --force-reeval: Force re-evaluation of existing results

Step 3: Review Results

Evaluation generates two output files in the tasks_eval_result/ directory: 1. Detailed Results (*_eval_results.json):
2. Summary Statistics (*_summary.json):

Comparison Table


Difference from Leaderboard

💡 Tip: After evaluation, you can submit your results to the Leaderboard for public comparison with other models.

Best Practices

✅ Do’s

  • Validate Format: Double-check all required fields before evaluation
  • Use Consistent IDs: Ensure task_id matches benchmark tasks exactly
  • Include Metrics: Add performance metrics for richer analysis
  • Document Model: Specify model_id and browser_id for reproducibility

❌ Don’ts

  • Don’t mix formats: Each benchmark has specific requirements
  • Don’t skip screenshots: LexBench-Browser and Online-Mind2Web need them
  • Don’t modify benchmark data: Use original task definitions
  • Don’t ignore errors: Address validation errors before proceeding

Troubleshooting

”Task ID not found in benchmark”

Cause: Your task_id doesn’t match any benchmark task
Solution: Use exact task IDs from the benchmark’s tasks.json

”Missing action_history field”

Cause: Online-Mind2Web requires action history
Solution: Add action_history array to your result.json

”No screenshots found”

Cause: trajectory/ directory is missing or empty
Solution: Ensure screenshots are in task_dir/trajectory/*.png

”Evaluation failed with API error”

Cause: Evaluation LLM API issues
Solution: Check OPENAI_API_KEY and network connectivity

Next Steps

  • View Examples: See Complete Workflow for end-to-end guide
  • Submit to Leaderboard: Share results publicly (Guide)
  • Custom Benchmarks: Create your own evaluation tasks (Documentation)