Scenario in benchmark · Version 1
A page the tool already finds has changed
A page the tool already returned is later updated.
How the tools performed
Every in-scope tool is visible. Outcomes come from current published Results for this scenario and benchmark version.
No published results for this scenario yet.
No published result does not tell you whether a tool has been tested. Test coverage is shown only for comparable published Results.
| Tool | Published outcomes | Test coverage | Result |
|---|---|---|---|
| No published result · alphabetical | |||
| Brave Search API | — | — | No published result |
| Exa | — | — | No published result |
| Firecrawl | — | — | No published result |
| GPT-5.6 terra | — | — | No published result |
| Linkup | — | — | No published result |
| OpenAI web search | — | — | No published result |
| Perplexity Sonar | — | — | No published result |
| SerpAPI | — | — | No published result |
| Serper | — | — | No published result |
| Tavily | — | — | No published result |
| Valyu | — | — | No published result |
| You.com | — | — | No published result |
Assessed = Pass + Fail + Not gradable. Gradable = Pass + Fail. Both use the published Result’s pinned-test denominator. — means not publicly available.
Test design
- Pinned test cases
- 1
- Disclosure
- 0 public · 1 withheld
- Capabilities exercised here
- Freshness
What this scenario evaluates
- Whether the tool already returned the page before the change was introduced.
- Whether the after-probe shows the updated live version of that same page.
- Whether the tool avoids serving a stale copy after the page changes.
- Whether the run is void when the before-probe does not establish prior return.
Specific test-case inputs and grading live on the related test-case pages.
How the results are graded
- Pass: the test-case expectations hold.
- Fail: an expectation demonstrably does not hold.
- Not gradable: the evidence cannot establish the outcome.
Version 1 uses test-case expectations; no scenario rubric is pinned.
Benchmark methodology →