Benchmark report

Task verified

5m 53s 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
Only the cleanup script: list-databases returned an object not an array (TypeError), and the idempotent re-run overwrote 60-cleanup.json, needing a rebuild from logs.

Where the time went

5:53 agent time
  • Research0:27
  • Attempt3:43
  • Verify1:43
5m 53sTotal elapsed
2:06Time to first success
0:00Waited on the owner

Judge reason

Live Turso Platform API run verified from saved code and responses. out/10-create-parent.json shows POST /v1/organizations/rickchen/databases HTTP 200 for tpcbench-20261110022038-841e43; 12/13 show items created with exactly 2 rows over https://<host>/v2/pipeline. out/20-create-branch.json shows the branch created HTTP 200 with the documented branch body seed {"type":"database","name":"<parent>"} (out/doc-features_branching.md: 'A branch is a separate database instance that is created from an existing database', same POST shown on that page), so not a plain copy; 22 shows the branch inherited id,name and 2 rows, so no 'branches do not inherit' citation was needed. 30 applies ALTER TABLE items ADD COLUMN note + one insert on the branch host only; 40 shows branch columns [id,name,note] with 3 rows and 41 shows the parent still [id,name] with 2 rows (confirmed independently in run-01-branch.log and 50-verification.json, all_assertions_pass true). Cleanup in run-02-cleanup.log is verbatim: DELETE branch HTTP 200 then GET 404 'record not found', DELETE parent HTTP 200 then GET 404, plus a final list with no tpcbench entries. Code (code/turso_branch_demo.py) uses urllib with ssl.create_default_context() over https URLs — TLS rule for Turso satisfied — and redacts jwt/password before saving; grep for 'ey...' JWTs across /workspace/home returns nothing and create responses show "password": "<REDACTED>". No mocks or hard-coded responses.

Attempt record

  1. 0:47Answered from saved key: TURSO_API_TOKENno wait
  2. —First success verified

Attempt artifacts saved.