Benchmark report

Task verified

6m 7s elapsed

The saved attempt met the documented success criterion.

Experience score

86/ 100

Agent-Ready
  • AInstall
  • SAuth
  • AExecute
  • SDocs
  • ACurrent
Experience measures friction in the tested task. The verdict says whether it succeeded.
Agent profile for this run: Install A, Auth S, Execute A, Docs S, Current AAInstallSAuthAExecuteSDocsACurrent
Agent profile · this run
Judge's note · what slowed the agent most
Resend's undocumented platform-wide 422 on every example.com/.org name forced four diagnostic probes and a fallback apex before the lifecycle could run.

Where the time went

6:07 agent time
  • Research0:19
  • Attempt3:55
  • Verify1:53
6m 7sTotal elapsed
2:53Time to first success
0:00Waited on the owner

Judge reason

Saved code (resend_domain_lifecycle.py, plain urllib against https://api.resend.com with Bearer key read from a private file) and per-step JSON evidence show the real lifecycle: POST /domains -> 201 id=5eb8d195-b5ed-4895-8851-e3244bd6742b with 4 required DNS records (DKIM TXT resend._domainkey..., SPF MX feedback-smtp.us-east-1.amazonses.com prio 10, SPF TXT v=spf1 include:amazonses.com ~all, CNAME rsend... -> send.forge.rmta.net), GET /domains/{id} -> 200, POST /domains/{id}/verify -> 200, GET again -> 200 status=pending, DELETE -> 200 {"deleted":true}, GET -> 404 Domain not found. run_output.txt prints every record (type/name/value) and 'FINAL DOMAIN STATUS: pending'; no verified claim, no dashboard, no mocking. One documented deviation: the mandated tpc-bench-af12b531.example.com was rejected by Resend with HTTP 422 'This domain has been registered already.' (evidence/01_create_domain.json); the agent reproduced the 422 for two other tpc-bench-<hex>.example.com/.org names and for apex example.com, and got a 201 control under an unrelated apex, so it ran the identical lifecycle on tpc-bench-af12b531.tpc-bench-example.com (same tpc-bench label, equally unpublishable DNS) and disclosed this as success_with_deviation. The substitution is a name forced by a platform-side block, not an easier operation, and every other instruction and success criterion is met with real API responses.

Attempt record

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

Attempt artifacts saved.