Firecrawl in Web Search for AI
Scenario-level performance from current published Results.
3 of 10 scenarios published
Firecrawl passed every graded scenario it has a published Result for.
How Firecrawl performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Answer Generation1 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The retrieved material doesn't support an answer | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFirecrawl acknowledged that the retrieved material did not establish Valve’s exact current employee count. It offered a dated estimate of 384 employees rather than claiming a live total. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The retrieved material supports an answer | No published result | ||
| The retrieved sources disagree with each other | No published result | ||
Web Retrieval2 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Search only these websites | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFirecrawl kept the search on docs.github.com: all 10 results came from that site, led by GitHub's 'About Copilot' page, and the GitHub Blog post that gives the answer (2021) did not appear. It returned a ranked list of pages rather than a written answer. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Something more famous has the same name | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFirecrawl returned ten results, all about Grafana Labs' Loki log system and none about the far more famous Marvel namesake. The top result, Loki's official documentation, says retention works through the Compactor and that the retention setting must be turned on; the second result shows that setting under the compactor block. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| A page on the web answers the question | No published result | ||
| The request uses different wording than the source | No published result | ||
Freshness3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A new page has just gone live | No published result | ||
| A page the tool already finds has changed | No published result | ||
| Content is removed from the source | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
Which scenarios have a Result?
A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.
What does each Result cover?
Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.
Out of 10 scenarios
The summary counts each of the 10 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Firecrawl was tested on it.