Benchmark report

Task verified

4m 7s 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 only overhead was loading WebFetch via ToolSearch and a deliberate 3s wait before the retrieve; the whole run finished in ~89s.

Where the time went

4:07 agent time
  • Research0:16
  • Attempt2:32
  • Verify1:19
4m 7sTotal elapsed
1:29Time to first success
0:00Waited on the owner

Judge reason

Saved code (resend-task/send_and_read.js, verify_raw.js) is real and unmocked: it reads the key from a private file, calls GET /domains (evidence 01 shows verified domain resend-bench.thefounderportfolio.com), POSTs /emails to the documented test recipient delivered@resend.dev only (evidence 02 request body, 03 response id 01a1ad9e-ddc0-7b55-8648-14d57d5ddafa with live cf-ray/ratelimit/x-resend-monthly-quota headers), then pull-reads GET /emails/01a1ad9e-... (evidence 04, HTTP 200) returning last_event "delivered", created_at "2026-11-05 21:30:32.438000+00", scheduled_at null and SES message_id. A no-SDK raw fetch re-read (05, status 200) and GET /emails?limit=20 filtered to the same id (06, matched_count 1) corroborate it. No webhook or dashboard used; no inbox created so no deletion needed. README/result.json match the saved responses exactly, and the report honestly cites Resend's gap (no per-event history or delivered_at field in the pull API) without inventing data.

Attempt record

  1. 0:43Answered from saved key: RESEND_API_KEYno wait
  2. —First success verified

Attempt artifacts saved.