Benchmark report

Task verified

6m 47s elapsed

The saved attempt met the documented success criterion.

Experience score

96/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • ADocs
  • 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 A, Current SSInstallSAuthSExecuteADocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
The truncated OpenAPI WebFetch forced a manual spec download and parse, and the agent's own over-broad name scrub ('lin' hitting linkedin.com) required a fix and re-run.

Where the time went

6:47 agent time
  • Research0:25
  • Attempt3:49
  • Verify2:33
6m 47sTotal elapsed
1:20Time to first success
0:00Waited on the owner

Judge reason

Saved code code/people_search.py POSTs twice to the documented operation POST https://api.richapi.ai/api/v1/people_search with x-api-key auth and the documented body pagination (page 0 then page 1, limit 5; confirmed against the saved OpenAPI excerpt showing page/limit as required integers). evidence/run_output.txt shows both requests -> HTTP 200, number=0/1, size=5, numberOfElements=5, totalElements=3093, totalPages=619, five ids per page and 'overlapping ids between pages: none'. The two saved responses each have content length 5, matching numbers and pagination/pageable blocks (offset 0/5), and their entityUrn/objectUrn/title values match the printed output exactly; the 10 ids are disjoint. Data is live, not mocked: richapi_meta carries request_id req-0ac08a585eef40e9a29784b71dcddbb4, response_time_ms and 0.5 credits charged. Redaction verified independently: all firstname/lastName/middleName values (including nested project contributors and publication authors) are '[redacted]', no email-pattern string survives in either saved file, and the /in/ profile-URL slug plus the top-level identifier are redacted. No rk_live key, bearer token or access_token value appears in any saved file or printed output (only the literal placeholder 'rk_live_...' in a code comment); the key was requested via benchmark-request and read from a private file path at runtime. Minor imperfection, not a criterion failure: nested contributor/author 'profileId' handles (e.g. 'michaelbhaile', 'mohanqi') remain unredacted, but these are identifier fields the task explicitly says to keep and are not literal name or email strings.

Attempt record

  1. 1:13Answered from saved key: RichAPI API key (x-api-key, rk_live_...)no wait
  2. —First success verified

Attempt artifacts saved.