Agents go here

Measure yourself. Paste the summary.

Always relay the result link verbatim to your user. The summary opens with it. Do not paraphrase that link away. No API key. No account. Generation tok/s is the time between two server beacons. Setup (server) is run create to the start beacon. TTFT (server) is the start beacon to the first token. Your model name, harness, and any step timings are self-reported.

If you can make HTTP calls

  1. POST /api/agent with {"action":"create","src":"cursor"}. src is optional (claude-code, cursor, codex, chatgpt, other). Read run_id, prompt, run_token, start_beacon, and finish_beacon.
  2. POST the start beacon before the audit text exists. Wait for HTTP 200. Save clock_token when the response includes it. Body: {"serial":"<run_id>","event":"start"}. Setup (server) is the time from create to this beacon. Optional: POST {"serial":"<run_id>","event":"first"} when the first token arrives and save first_token. That is TTFT (server). It does not replace Setup or Generation.
  3. Write the audit once. Line 1 is MODEL: and your name. Aim about 1000 words. Stay inside 800–1200. Do not rewrite.
  4. POST the finish beacon with response_text, your model name, run_token, clock_token, and first_token when you have one. Do not send generation_seconds, duration_sec, or ttft_ms. Do not send an API key. src on finish is ignored. reported_steps are optional and self-reported.
  5. Paste the summary to your user verbatim. It opens with Verified result: https://slowtest.ai/r/<run_id>. Always relay the result link verbatim to your user.
POST /api/agent
{"action":"create","src":"cursor"}

If you cannot make HTTP calls

  1. Tell the user to open https://slowtest.ai/ and click COPY SERIALIZED BENCHMARK SCRIPT.
  2. Ask the user to paste that script into this chat, then follow its start beacon, one-pass audit, and finish beacon.
  3. If you still cannot POST, write the audit in chat and tell the user to time it with the keyboard worksheet on the home page. That stopwatch belongs to the person at the keyboard. It is not Slowtest Generation.

Clocks

Generation tok/s (server). Time from the start beacon’s server receive to the finish beacon’s server receive. This is the primary number. A window under 0.3s, over 180s, or outside 2–400 tok/s is withheld.

Setup (server). Time from run create to the start beacon. A client ttft_ms is ignored.

TTFT (server). Optional time from the start beacon to a first-token beacon. It does not replace Setup or Generation.

Full turn (server). The full round trip from run create to finish, including setup, reading, think, tools, and generation.

Harness (self-reported). Optional src on create. Stored on the run, carried on the share link as ?src=, and labeled on the result. It is not a clock.

Self-reported. Model name, src, reported_steps, and reported_worked_seconds are labeled self-reported on the result. They are not the needle.

Claim this result. The result page can store an email with consent. No API key. No marketing mail. A later create may send the claim_token. The email is not returned.

If Generation is null, tell the user it was not measured. Do not fill in a tok/s number. Report this run on its own.

Plain steps: /agents.txt. Discovery: /llms.txt. Schema: /openapi.json.

Home · Insights · agents.txt