Benchmark report

Task verified

4m 51s 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 docs page is client-rendered, so the first fetch yielded no API details; the agent had to grep the HTML for the OpenAPI JSON URL.

Where the time went

4:51 agent time
  • Research0:22
  • Attempt2:48
  • Verify1:41
4m 51sTotal elapsed
1:20Time to first success
0:00Waited on the owner

Judge reason

Saved code (code/enrich_company.py, code/enrich_company.sh) POSTs to the documented operation POST https://api.richapi.ai/api/v1/enrich_company with x-api-key auth, exactly as the saved OpenAPI spec (docs/openapi.json, linked from https://app.richapi.ai/docs) defines: server https://api.richapi.ai/api/v1, securityScheme 'API Key' = apiKey header x-api-key, required body field url described as 'LinkedIn company page URL'. No domain input is documented for any company-enrichment op (/enrich, /enrich_companies_bulk also take URL/urns), so the task's LinkedIn fallback (linkedin.com/company/stripe) was correctly used. Transcript line 42 and evidence/enrich_company_stripe_stdout.txt show 'HTTP status: 200'; evidence/enrich_company_stripe_response.json is live (richapi_meta request_id req-8db393274c364839b8f279be9a2bae5d, response_time_ms 2826, credits charged 1.0, wallet_remaining 5018.94) and contains name 'Stripe', website 'https://stripe.com', industries ['Computer Software'], staff.total 16693, range 5001-10000 — matching the printed values exactly. A second independent curl run returned HTTP 200 with a distinct request_id and wallet_remaining 5016.94 (staff.total 16694, matching its own stdout), confirming non-mocked live billing. Independent grep of code, commands.md, result.json and evidence found no API key, bearer or access token value; the key was read from a file path outside the artifact dir and never echoed.

Attempt record

  1. 1:20Answered from saved key: RichAPI API keyno wait
  2. —First success verified

Attempt artifacts saved.