Benchmark report

Task verified

8m 59s elapsed

The saved attempt met the documented success criterion.

Experience score

99/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • SDocs
  • ACurrent
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 ASInstallSAuthSExecuteSDocsACurrent
Agent profile · this run
Judge's note · what slowed the agent most
Nothing substantive; ~6 doc fetches up front before any command, and the whole run reached first success in 217s with zero failed calls.

Where the time went

9:00 agent time
  • Research0:31
  • Attempt6:03
  • Verify2:26
8m 59sTotal elapsed
3:37Time to first success
0:00Waited on the owner

Judge reason

Saved evidence independently supports every criterion. commands/run.sh + transcript show `vercel env add TPC_BENCH_SECRET --environment production --sensitive --force --yes --scope tpc-cao < /tmp/private-tpc/secret.txt` (value piped on stdin, generated locally with secrets.token_hex(32)); outputs/06-env-ls.txt shows TPC_BENCH_SECRET value 'Hidden', type 'Secret', Production. outputs/07-deploy-stdout.txt shows a READY production deployment dpl_AdbXQbDayj9aZmX9WShkQ3TNiyoi at https://tpcbench-d1acff92.vercel.app (Vercel's own domain); outputs/09-response-headers.txt records HTTP/2 200 from server: Vercel with body {"sha256":"7049111336c7d69ca656d341d2df51f265c6949e1658b683b6a2a3c35f6c316e",...,"source":"process.env.TPC_BENCH_SECRET","secretLength":64}, and evidence/hash-comparison.txt prints LOCAL and REMOTE hashes both 7049111336c7...c316e, MATCH True (poll 08-poll.txt: 200 on attempt 1). evidence/deployed-source/api/hash.js reads process.env.TPC_BENCH_SECRET and returns only the digest - no hard-coded value, no mock; build logs (11) and runtime logs (10, recordsReturned 0) contain no secret, and a scan over saved files found 0 secret and 0 token occurrences. Project name tpcbench-d1acff92 only; outputs/13-remove.txt 'Removed 1 project', outputs/15 GET /v9/projects -> 404 not_found, remaining tpcbench-* projects NONE, and evidence/final-fetch.txt shows the final GET returning HTTP/2 404 x-vercel-error: DEPLOYMENT_NOT_FOUND. No bearer token appears in any saved file (token kept in /tmp/private-tpc/curl.cfg outside home, shredded at the end).

Attempt record

  1. 1:17Answered from saved key: Vercel API access tokenno wait
  2. —First success verified

Attempt artifacts saved.