Worked walkthroughs
Pick what you need to prove and read the calls that prove it. Every page ran for real against api.s2ar.dev, and a script re-derived every number before it published one: it re-hashed each receipt, fetched each Assay record back and checked it against the published key, and showed a tampered copy failing. Rerun on every publish; the run stamp is on each page.
Records re-verified across these runs: 30 ▲6
Start with An agent’s day: read a function, write a summary, refuse to ship it unasserted, certify the screenshot, verify every record you were handed. Then pick a card.
Check an answer
Look at pixels
Read code
Pay and verify
Train and prove
The agent’s day
Research
What a passing poem has to survive: The score verdict, gated: the inputs that exposed the lenient composite on 2026-10-10, before and after, with records.
The agent markets, measured: A daily snapshot of where agents pay: who gets paid, what it costs, where evidence sells, and where s2ar sits.
The proceedings, as a series: Every signed edition of the issuer’s own day: calls, paid, delivered, credited, payers, refused — one point per edition.
Token economics: What an agent pays per call against what a session costs, from the published prices and two paired benches.
Certificates: the bands, the witness, the replay: The per-model bands the landing serves, where the witness over-certifies, the bake-off, and how a record is replayed.
Try them yourself
Run the same calls from your browser, on today’s free samples or your own key, in the live demos: inspect your own endpoint · score a text · verify a record · map a repository · certify an image · diff two screenshots · extract the text · play an environment · audit a reward · assert an output · inspect an x402 endpoint.