The Prompting Company

Benchmark report

Task verified

7m 26s elapsed

The saved attempt met the documented success criterion.

Experience score

90/ 100

Agent-Ready
  • SInstall
  • SAuth
  • AExecute
  • 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 A, Docs S, Current SSInstallSAuthAExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Loops requires a 4-call create/update/publish dance before sending, and an undocumented LMX brace-escaping rule caused an HTTP 422 that forced a rewrite and rerun.

Where the time went

7:26 agent time
  • Research0:22
  • Attempt5:18
  • Verify1:46
7m 26sTotal elapsed
4:02Time to first success
0:00Waited on the owner

Judge reason

Saved code (loops-task/send_and_read_events.mjs) ran live against app.loops.so with a benchmark-provided key: out/10-api-key.json 200 {"success":true,"teamName":"Prompting Co"}; sender local part 'rick' discovered via GET /v1/email-messages/cmvh8mou7025a0jwmhscgh6tf (out/21); transactional created 201 id cmvh9ilwv00lc0jx550m8emmm and published (out/30, out/50). Exactly one send: POST /v1/transactional to loops-event-read@example.com (Loops' documented @example.com test domain, docs/transactional.md:266) returned HTTP 200 {"success":true} at Date Tue, 20 Oct 2026 22:36:14 GMT (out/70). Pull-style documented read GET /v1/transactional-emails/cmvh9ilwv00lc0jx550m8emmm/metrics, keyed to the recorded identifier, went from all-zero before send (out/60) to {"sends":1,"deliveries":0,"spamReports":0,"hardBounces":0,"softBounces":0} at 22:36:25 GMT and stayed stable across polls 3-6 and a later independent curl (out/80-*, out/90-metrics-final.json HTTP_STATUS:200). REPORT.md numbers match the saved responses exactly, and it states the real documented gaps (POST /v1/transactional returns only {success:true} with no per-message id; metrics body carries no event timestamp, so timestamps come from HTTP Date headers). No webhook, no dashboard, no mock. The earlier run aborted at HTTP 422 before any send, so only one email was transmitted.

Attempt record

  1. 1:00Answered from saved key: Loops API keyno wait
  2. —First success verified

Attempt artifacts saved.