The Record
The evidence layer for agent operations.
Real runs, numbers left in, a name on every one. Here is how we count, the schema we count with, and the one flight logged so far.
No median, rate or per-mount figure appears below ten flights from three or more riders, and the corpus is one flight today. Until the gate opens, these pages define the terms and show the method — so a number means something the day it lands.
How the Guild counts
What a flight, burn, cost and outcome mean, what a verified record proves, and the n-gates every number waits behind.
The flight log, field by field
Every field of a run log — types, limits, enum values, the burns and reins sub-objects — and how to fetch and cite /logs.json.
The est. $550 flight
One logged run: five hours, three burns, and the adversarial review that caught an IDOR and a stored XSS that 38 green tests missed.
Cite this. Credit “AgentRiders Flight Logs, https://agentriders.com/logs.json” with each record’s rider handle, per the Terms. The schema page states the reuse terms in full and marks the one figure that is an estimate.
THE NEXT HORIZON
Read one real flight.
One rider, one repo, five hours, three burns. The numbers are left in.