Benchmark report

Task verified

2m 51s 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; the only detour was auth.md's agentic OAuth flow needing a human browser claim, so the saved key was requested instead.

Where the time went

2:52 agent time
  • Research0:17
  • Attempt1:34
  • Verify0:59
2m 51sTotal elapsed
0:53Time to first success
0:00Waited on the owner

Judge reason

Saved search.mjs (/workspace/home/context-search/search.mjs) POSTs the exact query "PostgreSQL transaction isolation levels" to the documented endpoint https://api.context.dev/v1/web/search with Authorization: Bearer from a private key file, no mocking. response-evidence.json records a live HTTP 200 OK with Cloudflare/cf-ray headers, x-request-id 5dc01069-2858-4ed3-87fe-cb08073b607f, x-credits-used 2, x-ratelimit-remaining 907, cache_metadata status "miss", query echoed back, and 5 results in the documented shape (url, title, description, relevance, markdown, highlights). run-output.txt matches the evidence exactly: first result title "PostgreSQL Transaction Isolation Levels & MVCC | Mydbops", absolute URL https://www.mydbops.com/blog/postgresql-transaction-isolation-levels-guide, and a 242-char nonempty excerpt from results[0].description, with populated highlights.highlights as a second excerpt field. No documented gap needed to be cited.

Attempt record

  1. 0:51Answered from saved key: Context.dev API keyno wait
  2. —First success verified

Attempt artifacts saved.