The Prompting Company

Benchmark report

Task verified

3m 55s 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
No saved Postmark server token: the request was skipped and the test token is /email-scoped, so GET /senders and /domains 403'd and sender discovery had to be abandoned.

Where the time went

3:55 agent time
  • Research0:18
  • Attempt1:58
  • Verify1:39
3m 55sTotal elapsed
1:12Time to first success
0:00Waited on the owner

Judge reason

send_email.py POSTs JSON to the documented endpoint https://api.postmarkapp.com/email with the X-Postmark-Server-Token header; request.json byte-matches the payload literal in the code (From sender@example.com, To test@blackhole.postmarkapp.com - Postmark's documented test recipient, Subject 'Postmark API smoke test - transactional send', plain-text TextBody, MessageStream outbound). Transcript entry 45-46 shows the single live run: stdout 'HTTP status: 200 / MessageID: 364659fc-188e-484b-8668-27ff66b07bfb', matching response.json {ErrorCode:0, Message:'Test job accepted', MessageID:364659fc-..., SubmittedAt:2026-10-20T20:20:07.2680919Z, To:test@blackhole.postmarkapp.com} and response_headers.json (http_status 200, server Date 20:20:07, Ratelimit-Remaining 4999) - a live server response, not mocked or hard-coded. benchmark-request for a server token returned {"outcome":"skipped"}, so the agent used Postmark's official alternative: the saved auth.md states 'Send with the literal token POSTMARK_API_TEST to exercise the sending endpoints... Requests are accepted and validated'. Authentication is genuine - GET /server, /senders, /domains returned 403 ErrorCode 10 'The Postmark Test API Token may only be used on the /email endpoint', proving Postmark recognised and scoped the credential, and documenting why sender discovery was unavailable. REST API used, no SMTP or dashboard; exactly one send.

Attempt record

  1. 0:40Requested Postmark Server API tokendeclined automatically: campaigns don't wait for people
  2. —First success verified

Attempt artifacts saved.