Benchmark report
Task verified
3m 7s elapsed
The saved attempt met the documented success criterion.
96/ 100
Agent-Ready- SInstall
- SAuth
- SExecute
- ADocs
- SCurrent
Only minor: Clay has no single-company enrichment endpoint, so the agent had to read three doc pages to settle on query-mode Searches.
Where the time went
3:08 agent time- Research0:23
- Attempt1:27
- Verify1:18
Judge reason
Saved script clay/enrich_stripe.sh makes live authenticated calls (clay-api-key header, key read from a private file, never printed) to Clay's documented Public API: POST https://api.clay.com/public/v0/search/query-mode with query 'select from companies where domain = "stripe.com"' and POST /search/query-mode/{search_id}/run. Both saved status files record {"http_status":200}; create_search_response.json returns search_id search_0to97ot3ji3C5CJSoHy and run_search_response.json is a live documented-shape payload (data[], has_more, source_type, period_quota with used 576942 / resets_at 2026-11-10) whose data[0] is name 'Stripe', domain 'stripe.com', industry 'Technology, Information and Internet', size '5,001-10,000', linkedin_url .../company/stripe. printed_values.txt and the transcript run output (transcript idx 18-19) match that record exactly; the company was identified by domain as the docs allow. Agent correctly noted Clay documents no single-company enrichment endpoint and used the documented Searches operation, citing developers.clay.com/searches/advanced.md. Grep over all saved artifacts finds no token (only the literal header name with a shell variable in the script); no fabricated or mocked data.
Attempt record
- 1:00Answered from saved key: Clay API keyno wait
- —First success verified
Attempt artifacts saved.