Benchmark report
Task verified
4m 17s elapsed
The saved attempt met the documented success criterion.
96/ 100
Agent-Ready- SInstall
- SAuth
- SExecute
- ADocs
- SCurrent
Filter syntax is absent from the web docs, so the agent had to fetch and page through the 173KB reference_grammar.md from the API before writing the query.
Where the time went
4:17 agent time- Research0:22
- Attempt2:20
- Verify1:35
Judge reason
Saved script clay/clay_company_search.sh calls Clay's documented query-mode flow (POST /search/query-mode then POST /search/query-mode/{id}/run, limit 10) with the clay-api-key header. Both saved responses carry {"http_status":200}: 01_create_search_response.json returns search_0to9agrh9SXtAnqxNfT/source_type companies, 02_run_search_response.json returns data[10], has_more, source_type, period_quota. Filters were server-side in the query string (industry = "Software Development" and company_size = "201-500" and locations.any(is_headquarters = true and country_name = "Germany")), all three documented in the API's own reference.json/reference_grammar.md (company_size enum incl. "201-500", industry enum incl. "Software Development", locations.any with is_headquarters/country_name); no post-filtering. Independent re-parse of the saved response confirms all 10 rows have industry=Software Development, size=201-500, country=Germany, and that printed_output.txt matches the response field-for-field. No total is reported by the API and the report cites the documented 'count queries not available' gap. Grep over all artifacts found no token or key value, only $CLAY_API_KEY variable references; key was read from a private file outside home.
Attempt record
- 1:02Answered from saved key: Clay Public API keyno wait
- —First success verified
Attempt artifacts saved.