The Prompting Company

Benchmark report

Blocked by a prerequisite

4m 55s elapsed

An external prerequisite prevented the documented task from completing. Benchmark again

Experience score

55/ 100

Critical Gating
  • SInstall
  • BAuth
  • CExecute
  • SDocs
  • SCurrent
Experience measures friction in the tested task. The verdict says whether it succeeded.
Agent profile for this run: Install S, Auth B, Execute C, Docs S, Current SSInstallBAuthCExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Credential unavailability: the test token sends but 403s on every read endpoint, so the agent spent its remaining effort proving the endpoints exist in the OpenAPI spec instead of calling them.

Where the time went

4:55 agent time
  • Research0:14
  • Attempt3:14
  • Verify1:27
4m 55sTotal elapsed
—Time to first success
0:00Waited on the owner

Judge reason

Evidence shows real Postmark API traffic but the task's core read step never succeeded. send_and_read.js (saved, unmocked, raw fetch to api.postmarkapp.com) ran once: POST /email returned HTTP 200 {"Message":"Test job accepted","MessageID":"f680e7b0-0ad9-4050-b2c3-ebeb3c830f7e","SubmittedAt":"2026-10-20T22:45:51.9383048Z"} to test@blackhole.postmarkapp.com, so the identifier was recorded. The pull-style reads GET /messages/outbound/{id}/details and GET /messages/outbound?recipient=... both returned HTTP 403 {"ErrorCode":10,"Message":"The Postmark Test API Token may only be used on the /email endpoint."} (run_output.txt, responses.json), and GET /senders returned the same 403, so no Status/MessageEvents/timestamp data was ever obtained. The report correctly states success_criteria_met=false and fabricates nothing. Cause is an unavailable credential, not an API gap: Postmark does document the read endpoints (saved swagger-server.yml excerpt shows getOutboundMessageDetails -> OutboundMessageDetailsResponse requiring X-Postmark-Server-Token), the agent ran only with the documented POSTMARK_API_TEST fallback, two benchmark-request calls for a Postmark server token both returned {"outcome":"skipped"}, and the saved auth.md states 'There is no endpoint that issues tokens' (UI-only issuance), with sign-up unavailable. Setup completed: npm install postmark exited 0 with version 5.1.0 verified. No benchmark-first-success.json exists.

Attempt record

  1. 0:44Requested Postmark API keydeclined automatically: campaigns don't wait for people
  2. 3:29Blocked by a prerequisiteNo real Postmark Server API token: both benchmark-request credential requests returned outcome 'skipped', and Postmark's own auth.md documents token issuance only through the account UI, leaving the documented POSTMARK_API_TEST token which Postmark scopes to POST /email.

Attempt artifacts saved.