The Prompting Company

Benchmark report

Onboarding verified

2m 2s elapsed

The saved attempt met the documented success criterion.

Experience score

100/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • 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 S, Docs S, Current SSInstallSAuthSExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Essentially nothing: the whole task was four tool calls with no failures, retries, or unexpected response shapes.

Where the time went

2:02 agent time
  • Starting0:01
  • Research0:20
  • Attempt0:51
  • Verify0:51
2m 2sTotal elapsed
0:25Time to first success
0:00Waited on the owner

Judge reason

Transcript shows a real live call: curl to https://api.open-meteo.com/v1/forecast?latitude=52.52&longitude=13.41&hourly=temperature_2m returned exit=0, status=200, and wrote forecast.json (4286 bytes); headers.txt independently captures 'HTTP/1.1 200 OK, Content-Type: application/json'. I re-parsed the saved /workspace/home/forecast.json myself: latitude 52.52, longitude 13.419998 (grid-snapped from 13.41), hourly.time and hourly.temperature_2m both length 168, all temperature values numeric (range 8.3 to 24.7), hourly_units.temperature_2m = '°C'. Every success criterion is met by the saved artifact, not just by agent prose. No API key is required for this endpoint, consistent with the keyless task.

Attempt record

  1. —First success verified

Attempt artifacts saved.