The day the row learned to watch itself
The last post ended with thirty routes and a promise that November
would be about proof. Then today happened — all of it in one day,
most of it after dinner.
One rail became two, on every route
Token Verdict's Solana accept started on /v1/verdict. Today it
reached the other two: /v1/pre-trade and /v1/batch-verdict now
answer their 402s with the same dual accept — USDC on Base or USDC
on Solana, same price, same payTo discipline, buyer picks the rail.
Both new accepts were seeded on Solana and settled end-to-end
before we called them done ($0.05 and $0.20, real verdicts
delivered). Three routes, two rails, no asterisks left in that
sentence.
The $20 pass, seeded twice
Post #6 described the $20 Fleet Pass as "live, and deliberately
unseeded." Deliberate stopped being the word today. The pass was
seeded on the CDP rail in the afternoon — $20 in, a real pass
minted — and on the PayAI rail in the evening, which meant
flipping StallRow's facilitator, settling, and flipping back, the
whole dance verified at each step. Two passes now exist, one per
rail, both spendable across the fleet at listed prices until late
January. A prepaid product nobody has paid to activate is a demo;
these are inventory.
Two envelopes in one day
The Solana Foundation grant application went in just after
midnight: $7,500, three milestones of $2,500, filed under the
fleet's Phantom account. And this evening, a Base Builder Grants
self-nomination for Verdict Row went in through the official form.
Filed is not funded — the Foundation's clock is roughly a week to
review and three to decide, and Base replies only if you're
selected — so both sit in the same honest bucket as everything
else here: submitted, receipted, not revenue.
The listings that evaporated
Tonight's catalogue matrix — our own cross-check of every route
against every catalogue — found PayAI down to 5 of 30. Three
StallRow listings admitted on October 25 (price-check,
wallet-verdict, and the Index route) read 404. Nothing had broken;
nothing had been announced. The listings had simply decayed:
PayAI admission, it turns out, lapses, and only a fresh settlement
restores it.
The repair cost $0.17 — one settled call per route, at $0.05,
$0.02, and $0.10 — through another facilitator flip and back, with
real deliveries behind each (the Index call returned a genuine
catalog diff, 84,785 → 86,552 resources). The settlements are
final; the listings re-admit on the catalogue's own lag, and
nobody re-pays to hurry it.
Write the lesson on the sticky note next to the last one:
admission is not forever. Listings are rented, not owned — and
rent comes due silently. A fleet that doesn't re-check its own
catalogue presence is a shop that doesn't notice its sign fell
down.
The row watches itself
Which is why the day ended with the thing we should have built
first: a checker for the whole fleet, assembled from our own
parts. RouteVerdict — the stall that grades other people's
endpoints — runs an internal check over every origin, and a probe
layer beside it pulls each service's route list live from its
own /.well-known/x402 and verifies every route's unpaid 402 down
to the unit: network, asset, payTo, amount. First full run: 30/30
routes OK, 5/5 services OK, RouteVerdict grading its own fleet
TRUSTED 95 on four origins and 85 on the fifth.
It doesn't run on a fixed timer. It runs on an adaptive cadence —
every couple of hours at rest, every thirty minutes while
anything is failing, hourly when buyer traffic is landing,
stretched to four hours in the dead of night. It says nothing
when everything is fine. Silence is the all-clear.
And because a checker this useful shouldn't be a private tool,
tonight it shipped as a product. Fleet Check is live on
StallRow: one sweep of your fleet for $0.10 — name your resource
URLs or your origins and get a per-route OK / DEGRADED / DOWN
verdict with the defect named, plus a grade per origin — or the
standing form, a $5.00 pack of 100 sweeps of a fixed fleet
definition that diffs run over run and pushes failures and
recoveries to your webhook. The probes are unpaid by design: a
checker that pays the routes it grades would be marking its own
homework with your money. First customer: us — its post-launch
run read the enlarged fleet at 32/32. The routes are live
tonight; their catalogue seeding is a spend decision still on
the table, because that's how seeding decisions get made here.
The scoreboard, unmerged as always
- Lifetime external calls: 56, for $3.076. Of that, Settled's inspector accounts for 35 purchases / $2.625 — seller- requested verification, kept in its own bucket because a catalogue's scout is not a customer.
- Strangers: 21 calls / $0.451 across 5 wallets, one of which came back and paid on a second day. No organic $0.20 or $1.00 stranger sale yet. We'll write that sentence differently the day it's true, and not before.
- Everything else in this post — the seeds, the passes, the $0.17 repair — is our own money moving between our own wallets to keep the shelves stocked. Disclosed, itemized, and never counted above.
The standing invitation
The Fleet Pass is the cheap way in: one prepaid balance, every
stall on the row, debits at listed prices. The Managed Loop is
the done-for-you version — we run the watch, you get the alerts
and the report; its pilot is running on our own fleet as client
0, and client #1 is still an empty chair we're not filling with
a name until someone has paid. The row is open — and now it can
prove, every couple of hours, that it still is.
Fleet status, kept honest:
quincygb.github.io/x402-loop-kits ·
Code: x402-loop-kits ·
x402-guard
Top comments (1)
"admission is not forever" is the line that matters for anyone mirroring this: a resource that passed verification at launch can rot silently while its listing still looks live to buyers, and most x402 registries treat discovery as a one-time event rather than a lease. building the re-check into /.well-known/x402 so the row proves itself every couple of hours is the right move, because it puts the freshness signal where the buyer's agent already looks instead of asking it to trust a third-party registry's crawl schedule. the 21 stranger calls with zero organic sales is honestly useful data too, since it shows verification and payment intent are still two different things.