Benchmark report

Task verified

6m 20s 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
Learning from GET /search/query-mode/reference that current-employer domain matching needs clay.filter_to_companies(), not company.domain inside experiences.any().

Where the time went

6:20 agent time
  • Research0:26
  • Attempt3:10
  • Verify2:44
6m 20sTotal elapsed
2:15Time to first success
0:00Waited on the owner

Judge reason

Saved code (code/clay_common.py, code/people_search_paginated.py) calls the documented Clay Searches operation live over HTTPS with the clay-api-key header read from a private file: POST /search/query-mode created search_0to9exnBdKHMpSeauMo, then two separate POST /search/query-mode/{id}/run calls with {"limit":5} - the stateful-iterator pagination the fetched docs describe ("To get the next page, call .../run again while has_more is true"). Both saved responses record http_status 200 with 5 people each and has_more true; ids [802339914,233391835,418095447,183898033,783995594] and [4217326,208176343,680862030,104635603,313606622] are disjoint (verified set intersection empty). outputs/run_stdout.txt ids/titles/pagination match the saved page files exactly (programmatically cross-checked). All name/first_name/last_name/linkedin_url fields in every saved file are "[redacted]"; my own regex sweep of /workspace/home found zero email addresses and zero linkedin.com/in slugs, and identifiers, titles, has_more, source_type, limit and period_quota are preserved. No token or key value appears in any saved file or printed output (key passed only as a file path). API reports no total count, consistent with the docs line "Count queries ... aren't available through the Public API". One transient slip: the first run saved and printed an unredacted LinkedIn vanity URL embedding a name (transcript idx 65); the agent detected it, extended redaction and re-ran, so final artifacts are clean. Nothing fabricated or mocked.

Attempt record

  1. 0:57Answered from saved key: Clay Public API keyno wait
  2. —First success verified

Attempt artifacts saved.