Benchmark report

Task verified

4m 11s elapsed

The saved attempt met the documented success criterion.

Experience score

94/ 100

Agent-Ready
  • AInstall
  • SAuth
  • SExecute
  • ADocs
  • 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 A, Current SAInstallSAuthSExecuteADocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
One rejected benchmark-request JSON schema, plus the create response omitting email_address so an extra GET /inboxes/{id} read-back was needed for the deliverable address.

Where the time went

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

Judge reason

Saved runnable code (resend-inbox-task/create_and_delete_inbox.mjs + api.mjs) calls the live Resend API with a Bearer key read from a private file. Evidence 02-create-and-delete-run.txt and full-transcript.json show POST https://api.resend.com/inboxes -> HTTP 201 {"object":"inbox","id":"9380b458-73f1-4d72-b18f-54ab65de1600"}; because the create body returned only id, the script reads back GET /inboxes/{id} -> 200 with email_address bench-1794247613674@resend-bench.thefounderportfolio.com on a domain whose DKIM/SPF and inbound MX are all 'verified' with capabilities.receiving enabled (00-list-domains.json, 01-domain-and-inboxes.txt), and prints both id and deliverable address. DELETE /inboxes/{id} -> HTTP 200 {"deleted":true}, and the bounded (<=60s) poll's first read returned HTTP 404 {"message":"Inbox not found"}; an independent post-run check (03-post-run-verification.txt) re-confirms 404 and an empty GET /inboxes list. No mocking or hard-coding; transcript tool results match the saved artifacts byte-for-byte.

Attempt record

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

Attempt artifacts saved.