Benchmark report

Task verified

6m 37s elapsed

The saved attempt met the documented success criterion.

Experience score

100/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • SDocs
  • 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 S, Current SSInstallSAuthSExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Minor only: scraping the docs HTML/OpenAPI to confirm endpoints, and a stale 200 [] from the deleted project's REST host needing a second poll script until 530.

Where the time went

6:37 agent time
  • Starting0:01
  • Research0:20
  • Attempt4:31
  • Verify1:45
6m 37sTotal elapsed
2:17Time to first success
0:00Waited on the owner

Judge reason

Saved code and runtime output prove the full HTTP-only flow against real Supabase. code/01-create-project.mjs POSTed https://api.supabase.com/v1/projects -> 201 creating tpcbench-8ca01a764b (ref wbrxxuqdhzpdqcidtqbk); code/03-create-table.mjs created public.items via POST /v1/projects/{ref}/database/query -> 201 with an information_schema check returning the table; code/05-postgrest.mjs used only global fetch() to https://wbrxxuqdhzpdqcidtqbk.supabase.co/rest/v1/items, POST -> 201 returning ids 1/2 (widget 7, gadget 42) and GET ?select=id,name,qty&order=id -> 200 with content-range 0-1/2 and the same two rows; transcript stdout at the 05 step prints 'id=1 name=widget qty=7 / id=2 name=gadget qty=42 / row_count=2', matching evidence/05-postgrest-insert-select.json exactly. No pg/postgres/ws/net/tls import or Pool/Client/WebSocket appears in any code file, so no TCP or WebSocket DB connection was opened; PostgREST was authenticated with the project's own secret API key, not the management token. Cleanup: DELETE /v1/projects/{ref} -> 200 with the delete body, follow-up GET -> 404 'Project not found', GET /v1/projects no longer lists it, and evidence/07 shows the project PostgREST host returning 530. My own grep of all saved artifacts for sbp_/sb_secret_/JWT/password-bearing postgres URLs found nothing unredacted; the db_pass was crypto-random in memory only. TLS evidence is the saved https:// URLs, as the task allows.

Attempt record

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

Attempt artifacts saved.