Benchmark report

Task verified

5m 55s elapsed

The saved attempt met the documented success criterion.

Experience score

98/ 100

Agent-Ready
  • AInstall
  • SAuth
  • SExecute
  • SDocs
  • SCurrent
Experience measures friction in the tested task. The verdict says whether it succeeded.
Agent profile for this run: Install A, Auth S, Execute S, Docs S, Current SAInstallSAuthSExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
No Turso SDK or CLI was available in the environment, so the agent had to hand-write a Hrana /v2/pipeline HTTP client before it could connect.

Where the time went

5:56 agent time
  • Research0:42
  • Attempt3:39
  • Verify1:34
5m 55sTotal elapsed
2:29Time to first success
0:00Waited on the owner

Judge reason

Saved code and live API responses support every criterion. Database tpcbench-6a1cd857befb was created via POST /v1/organizations/rickchen/databases (outputs/04, HTTP 200). A read-only scoped credential was minted through the documented Platform API (code/03-create-readonly-token.sh: POST .../auth/tokens?expiration=never&authorization=read-only, outputs/07 headers HTTP 200, body redacted); its decoded claims show a=ro. Connecting with only that token over https://<db>.turso.io/v2/pipeline with ssl.create_default_context (check_hostname=True, CERT_REQUIRED) returned HTTP 200 with rows alpha/beta for SELECT, and the INSERT was refused: 'Operation was blocked: SQL write operations are forbidden (current session doesn't have write permission)' code BLOCKED (outputs/08). Revocation used the documented invalidate-tokens endpoint POST .../auth/rotate (HTTP 200), after which the same token got HTTP 401 'role was invalidated after token was issued' (outputs/10). Cleanup: DELETE returned 200 {"database":"tpcbench-6a1cd857befb"}, follow-up GET returned 404 'record not found', and the list endpoint shows no tpcbench-* databases remain (outputs/11). No JWT, password, or password-bearing connection string appears in any saved file (grep for eyJ* found none; create-database response password field is empty). Nothing mocked or hard-coded; all responses carry live CloudFront headers and timestamps.

Attempt record

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

Attempt artifacts saved.