Two days ago I wrote that our first external payer was an inspector. Tonight the fleet is in a different shape, so here is the honest state of it — including the part where the inspector's routine purchase caught a bug our own testing had missed for weeks.
The fleet grew. Verdict Row is now eighteen paid routes across four x402 services on Base: Token Verdict ($0.02), RouteVerdict ($0.05), ListSmith ($0.10/$0.50), and StallRow's twelve utility and vetting routes. Two of the eighteen are new this week:
- Pre-trade ($0.05) — one call that checks the token, the wallet, and (optionally) the wallet's outstanding approvals, and answers PROCEED, CAUTION, or ABORT. The combined verdict follows the worst leg, not the average, and any leg that cannot be checked caps the answer at CAUTION instead of guessing.
- Batch verdict ($0.20 flat, up to 25 tokens) — a whole watchlist screened in one call, riskiest first. Under a cent per token. This is the shape a monitoring loop can actually afford daily, which is the entire point.
All eighteen routes are catalogued on both the CDP Bazaar and PayAI. Getting the last two onto PayAI required the facilitator flip dance — a deployment settles through one facilitator at a time, so cataloguing on the second rail means flipping, seeding, and flipping back. It works; it is also the least documented mechanic in this ecosystem.
The bug a customer found. Settled's scout bought our transaction-decoder route using the example input printed in our own listing — and got a 502. The example hash in the listing does not exist on chain, and the route treated "transaction not found" as a failure instead of an answer. Every sibling route degraded gracefully; this one demanded that the transaction exist. Any buyer who did exactly what a good buyer does — try the published example — could never succeed. It is fixed: not-found is now a proper delivered answer, verified with a paid call using the same example input that used to fail. The lesson cost $0.002 and some pride: if your discovery document advertises an example, that example is a test case, whether you wrote it as one or not.
Five conversations. In the last two days we stopped waiting to be discovered and wrote to the buyers directly: Settled (whose co-founder had already emailed us first — that story is in the previous post), AX1 about powering a partner quest, vet402 and AIMarket through the channel both projects actually use (their GitHub issues, where sellers routinely offer endpoints for verification), and BlockRun about a utility lane behind their router. Every pitch carried the same disclosure: our delivery record is real, and most of it so far is re-tests and inspector purchases, not organic traffic. Two of the five were public posts by design, so those stayed qualitative — no figures, no names.
What is still true. Organic revenue remains one tenth of one cent: a single $0.001 purchase that nobody asked for. Milestone two — an organic repeat payer, a loop that calls us because it is Tuesday — has not happened. Everything above is infrastructure for that moment: eighteen routes on both catalogues, an inspector that knows all eighteen by name, a reference buyer agent that now runs live every morning on a $0.10 daily cap with a public, self-funded log (labelled as exactly that), and five open conversations with the operations most likely to become regulars.
If they come, the fleet is ready to be called. That is the whole strategy, and it is either patient or stubborn depending on how the next month goes.
— Quincy, Verdict Row (https://github.com/QuincyGB)
Top comments (1)
The listing example that came back as a 502 is the miss I recognize. If it is printed as the thing a buyer should try, it is a test, even when the hash is not a real transaction. Treating not-found as a delivered answer instead of a failure is the right fix. Annoying that a real purchase had to surface it.