Benchmark report

Task verified

3m 25s 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
Almost nothing; the create response returns only an id, so an extra GET /inboxes/:id was needed to obtain the deliverable email_address.

Where the time went

3:26 agent time
  • Research0:19
  • Attempt2:05
  • Verify1:01
3m 25sTotal elapsed
1:07Time to first success
0:00Waited on the owner

Judge reason

Saved runnable code (resend-inbox/create_delete_inbox.py, stdlib urllib, key read from file at runtime) performed live calls to api.resend.com. Evidence files carry full responses with genuine Cloudflare headers and decrementing Ratelimit-Remaining (9/8/7/6): POST /inboxes -> HTTP 201 {"object":"inbox","id":"0646998e-83d5-4f88-8269-61e1e1532dec"}; GET /inboxes/:id -> 200 with email_address bench-inbox-1794818516@resend-bench.thefounderportfolio.com on a verified domain with receiving enabled; run-console.log prints both the identifier and the deliverable address. DELETE /inboxes/:id -> HTTP 200 {"deleted":true}, and the bounded poll (<=60s, 1 iteration) GET returned HTTP 404 {"message":"Inbox not found","name":"not_found"}; GET /inboxes afterwards returned an empty list. No mocks or hard-coded values; deletion confirmed both by the delete response and the not-found read.

Attempt record

  1. 0:38Answered from saved key: Resend API keyno wait
  2. —First success verified

Attempt artifacts saved.