Benchmark report

Task verified

5m 42s elapsed

The saved attempt met the documented success criterion.

Experience score

93/ 100

Agent-Ready
  • SInstall
  • AAuth
  • SExecute
  • SDocs
  • SCurrent
Experience measures friction in the tested task. The verdict says whether it succeeded.
Agent profile for this run: Install S, Auth A, Execute S, Docs S, Current SSInstallAAuthSExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Discovering that GET /senders rejects the server token and needs a separate account token, plus ~15s of outbound-search indexing lag.

Where the time went

5:43 agent time
  • Research0:20
  • Attempt3:30
  • Verify1:52
5m 42sTotal elapsed
2:23Time to first success
0:00Waited on the owner

Judge reason

Saved run.mjs makes live HTTPS calls to api.postmarkapp.com with no mocks. out/02-send-response.json shows POST /email HTTP 200, ErrorCode 0, MessageID c12e44fd-94f6-4a81-95ca-699b45bf4f64, To test@blackhole.postmarkapp.com (Postmark's documented black-hole recipient, shown in the saved request body). Pull read-backs: out/03-outbound-search.json (GET /messages/outbound?recipient=test%40blackhole... HTTP 200, TotalCount 23, matched MessageID, Status Sent) and out/04-message-details.json (GET /messages/outbound/{id}/details HTTP 200) returning Status Sent, ReceivedAt 2026-11-09T13:26:51-05:00 and MessageEvents [{Type: Delivered, Recipient: test@blackhole.postmarkapp.com, ReceivedAt 2026-11-09T13:26:51-05:00, Details.DeliveryMessage 'smtp;250 2.0.0 OK (sandbox blackhole)'}]. The details payload includes the full raw MIME Body with X-PM-Message-Id matching the send response, and the search artifact contains 22 unrelated prior account messages, both inconsistent with fabrication. The final report's quoted status/event/timestamps match the artifacts exactly. No webhook or dashboard was used; no inbox was created, so no deletion response is required. Sender was discovered via GET /senders (out/01-sender-signatures.json, rick@promptingco.com, Confirmed true). Setup was clean: docs read via WebFetch, server and account tokens obtained through benchmark-request, no SDK needed (plain Node fetch).

Attempt record

  1. 1:46Answered from saved key: Postmark Account API Tokenno wait
  2. —First success verified

Attempt artifacts saved.