Benchmark report

Task verified

4m 32s 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
Essentially nothing: first success recorded at 84s with every API call succeeding on the first attempt.

Where the time went

4:32 agent time
  • Research0:23
  • Attempt2:37
  • Verify1:32
4m 32sTotal elapsed
1:24Time to first success
0:00Waited on the owner

Judge reason

Saved code and live responses support every criterion. work/code/01-create-db.sh created tpcbench-af7f292f via POST https://api.turso.tech/v1/organizations/rickchen/databases (HTTP 200, Hostname tpcbench-af7f292f-rickchen.aws-ap-northeast-1.turso.io); 02-mint-db-token.sh minted a database-scoped token (HTTP 200, saved only as "<redacted-database-auth-token>"); 03-http-sql.mjs uses only Node global fetch against https://<host>/v2/pipeline (single import node:fs, no @libsql, no ws/net/tls) and got HTTP 200 for CREATE TABLE items, INSERT (affected_row_count 2, last_insert_rowid 2) and SELECT returning rows [1,widget,7] and [2,gadget,42] — stdout 03-http-sql-stdout.txt matches 03-http-sql-responses.json exactly, so nothing is mocked or hard-coded. Cleanup: DELETE returned 200 {"database":"tpcbench-af7f292f"}, follow-up GET returned 404 "record not found", the org list shows 0 matches, and a pipeline POST to the dead host returned 404 "Namespace ... doesn't exist". TLS is evidenced by the https:// URLs on every request. My own grep for JWT patterns over /workspace/home found 0 matches; the only "password" occurrence is the empty field in the create response.

Attempt record

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

Attempt artifacts saved.