scrapingbench

Context.dev for AI agents: benchmark results

Context.dev finished the most scrape tasks (92%, of 8 providers) and the most map tasks (47%, of 2 providers), but neither lead is big enough to rule out chance. It had the lowest cost per finished task on map (1.84¢), counting API and model spend, failures included.

Against Firecrawl, on the same tasks: scrape 92% vs 90% of tasks done, at 0.72¢ vs 1.22¢ per finished task; search 75% vs 85% of tasks done, at 1.82¢ vs 3.04¢ per finished task; map 47% vs 40% of tasks done, at 1.84¢ vs 3.35¢ per finished task; crawl 60% vs 50% of tasks done, at 7.58¢ vs 14.2¢ per finished task. The scrape, search and map gaps in tasks done are too small to rule out chance. On crawl, neither led, so the benchmark didn't test the two against each other. Firecrawl vs Context.dev, track by track.

Context.dev (content API) was tested on scrape, search, map and crawl. It got the same tasks, the same model (Claude Haiku 5.5), the same prompt and the same limits as every other provider, and a script checked every answer.

Context.dev website

Scrape 60 tasks · Read one page and pull out exact fields: prices, versions, install commands.

Tasks done
92%
55 of 60
95% interval
90%–100%
Cost per finished task
0.72¢
Median time
3.7 s

1st of 8 on tasks done. Context.dev finished the most scrape tasks, but its lead over Linkup, Firecrawl and TinyFish (90%) is too small to rule out chance.

Raw output, no model: the API's own response held every answer on 51 of 55 applicable tasks (93%), at 0.26¢ of API spend per finished task.

Tuned settings, frozen before the run: 55 of 60 (92%), against 92% with defaults.

Scrape results, Context.dev highlighted
ProviderTasks done95% intervalCost per finished taskMedian time
Context.dev55 of 60 (92%)90%–100%0.72¢3.7 s
Linkup54 of 60 (90%)90%–90%0.60¢3.4 s
Firecrawl54 of 60 (90%)90%–90%1.22¢3.3 s
TinyFish54 of 60 (90%)80%–92%0.43¢3.5 s
Scrapfly53 of 60 (88%)80%–90%0.61¢5.0 s
Jina52 of 60 (87%)60%–92%0.57¢3.8 s
Browserbase49 of 60 (82%)78%–100%1.12¢3.3 s
Spider12 of 60 (20%)4%–100%2.48¢4.6 s

All scrape results and charts

Map 15 tasks · List every URL in a section of a site nobody has indexed yet.

Tasks done
47%
7 of 15
95% interval
11%–100%
Cost per finished task
1.84¢
Median time
6.1 s

1st of 2 on tasks done. Context.dev finished the most map tasks, but its lead over Firecrawl (40%) is too small to rule out chance.

Raw output, no model: the API's own response held every answer on 3 of 15 applicable tasks (20%), at 1.10¢ of API spend per finished task.

Map results, Context.dev highlighted
ProviderTasks done95% intervalCost per finished taskMedian time
Context.dev7 of 15 (47%)11%–100%1.84¢6.1 s
Firecrawl6 of 15 (40%)11%–100%3.35¢11 s

All map results and charts

Crawl 10 tasks · Read a whole section of a site and return every record in it.

Tasks done
60%
6 of 10
95% interval
0%–82%
Cost per finished task
7.58¢
Median time
18 s

2nd of 3 on tasks done. Context.dev is behind Scrapfly (70%), but the gap of 10 points is too small to rule out chance.

Crawl results, Context.dev highlighted
ProviderTasks done95% intervalCost per finished taskMedian time
Scrapfly7 of 10 (70%)0%–95%2.88¢14 s
Context.dev6 of 10 (60%)0%–82%7.58¢18 s
Firecrawl5 of 10 (50%)0%–68%14.2¢60 s

All crawl results and charts

Context.dev compared

Other providers