Benchmark report

Task verified

13m 30s elapsed

The saved attempt met the documented success criterion.

Experience score

100/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • SDocs
  • SCurrent
Experience measures friction in the tested task. The verdict says whether it succeeded.
Agent profile for this run: Install S, Auth S, Execute S, Docs S, Current SSInstallSAuthSExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Essentially nothing - docs fetch, key request and the live call completed in ~55s with no failed attempts or retries.

Where the time went

13:30 agent time
  • Starting0:35
  • Research1:43
  • Attempt6:06
  • Verify5:07
13m 30sTotal elapsed
0:55Time to first success
0:00Waited on the owner

Judge reason

Saved code (tavily-daterange/search_date_range.py) makes a real urllib POST to https://api.tavily.com/search with Bearer auth; evidence/request.json shows body {query:'PostgreSQL 17 release', topic:'news', max_results:10, start_date:'2024-09-01', end_date:'2024-10-31'} - documented GA parameters per the fetched API reference (only include_published_date is beta, and it was avoided via documented topic='news'). run_output.txt records HTTP 200 and evidence/response.json is a genuine live payload (request_id 20352598-28a6-4685-996b-04a3d6f3e37f, response_time 1.08, per-result ids/scores). Exactly 3 results returned, every one carrying a published_date inside range: 27 Sep 2024, 21 Oct 2024, 24 Oct 2024. No dates in the query text and no local filtering - the script prints all results unconditionally. No mocking or hard-coded data.

Attempt record

  1. 6:06Answered from saved key: Tavily API keyno wait
  2. —First success verified

Attempt artifacts saved.