Benchmark report

Task verified

8m 58s 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
Waiting on readiness: the poll script hit the 120s tool timeout, went background, and a blocked `sleep` forced extra polling detours before work resumed.

Where the time went

8:58 agent time
  • Research0:21
  • Attempt7:02
  • Verify1:35
8m 58sTotal elapsed
5:21Time to first success
0:00Waited on the owner

Judge reason

Saved zero-dependency Node code (work/code/*.js, Node 24 fetch only; transport-proof.txt shows no node_modules and no net/tls/ws/pg/WebSocket/5432 matches) created project tpcbench-41d2750c54 (ref mqpptcjxyvfjdzzysxja) via POST https://api.supabase.com/v1/projects -> 201, created table public.items via POST .../database/query -> 201 with verify returning [{table_schema:public,table_name:items}], then over PostgREST inserted two rows (POST https://mqpptcjxyvfjdzzysxja.supabase.co/rest/v1/items -> 201, body [{id:1,alpha,11},{id:2,beta,22}]) and read both back (GET .../items?select=id,name,qty&order=id.asc -> 200, same two rows). Printed log out/04-postgrest.log matches evidence/http-insert-select-rows.json exactly (row count: 2). TLS evidenced by the saved https URLs. Cleanup: DELETE https://api.supabase.com/v1/projects/mqpptcjxyvfjdzzysxja -> 200 with body {ref:mqpptcjxyvfjdzzysxja,...}; follow-up reads show POST .../database/query -> 404 'Resource has been removed', GET .../api-keys -> 404, PostgREST GET -> 401 'Invalid API key', and GET /v1/projects -> 200 with 0 matching entries. PostgREST was authenticated with the project's own 'secret' API key (fetched via /api-keys?reveal=true), not the management token; grep across all code, outputs and evidence found no JWT, sb_secret, sbp_ or postgres:// credential strings - db_pass is generated in-process and written as [REDACTED]. No mocked or hard-coded responses.

Attempt record

  1. 0:38Answered from saved key: SUPABASE_ACCESS_TOKENno wait
  2. —First success verified

Attempt artifacts saved.