Three public lanes. One gate. One audit chain.
One page for the lattice — the paid lanes that run through the IronBridge gate, and the receipt every call leaves behind. The full lattice is four planned primitives — data, court records, settlement, generation — each inheriting the off-LLM capability gate and the LAW-25 hash-chain audit underneath. Page Audit is the stranger $0.10 job; GITLAWB is live; BNKR is unfulfilled (do not pay) ($0.10 USDC per call → treasury Safe, re-walkable receipt). GITLAWB has been proven end-to-end by an operator self-test — real $0.10 USDC split on-chain, not a customer sale. BNKR fulfillment is down — do not send a dime. Page Audit is the payable stranger path. Page Audit’s no-money challenge, malformed-proof, and forged-payment refusal paths are public; its standard-client adapter and first stranger-paid call remain pending. No external customer has paid any lane yet — the lanes are open, the traction isn't claimed.
The optional inference brain. The model is routed through BNKR's multi-provider LLM gateway — but it still sits below our signer, so a smarter model can ask for more and still can't move your money. BNKR fulfillment is down — do not send a dime. An older operator self-test once cleared a metered completion, but stranger truth today is unfulfilled — that was an operator self-test, not a stranger, so it stays a proven rail, not external traction. The settlement/trading resale lane is still parked — no per-call terms confirmed in writing yet, so we won't label that leg live or fake a demo until a stranger can pay one and re-verify it.
The rails an app plugs into — add two lines and your app takes a paid call, can bound an agent's spend below the LLM (cap built, not yet exercised by an external payment), and emits a re-walkable receipt. The gate + audit, dropped into anyone's app. The atomic on-chain split (95.5% dev / 4.5% treasury, one Base tx) runs on every paid call.
Submit one HTTPS URL and receive a receipt-chained A–F integrity report covering parse errors, mojibake, link syntax, title, charset, and viewport. It performs one fetch, follows no redirects, and does not crawl.
Settled on Base L2 · pay-per-call in $USDC · stranger $0.10 job: Page Audit; live: GITLAWB; BNKR unfulfilled · no verified outside sales reported — the services are open and operator samples are labeled
HTTP 402 prices the call. IronBridge checks the payment and records the result.
Most agent-payment rails stop at “paid.” IronBridge gives the buyer a keyless receipt that binds the payment to the exact result — sealed to a public hash chain with date-specific Base anchors. Verify the returned linkage window yourself; leaf preimages and a pinned public ZK verifier are not yet exposed.
Result-bound, not just paid.
The receipt commits to the sha256 of what you got back, tied to the payment transaction. Payment and proof in one call.
Keyless linkage, with public limits.
You can re-walk the linkage in the public response window and check date-specific anchors on Base. Leaf preimages and full-history replay are not public yet, so those layers remain operator-attested.
Custom transport, public receipt schema.
The current transport uses IronBridge’s pay-then-prove transaction-hash extension. Standard x402 v2 client compatibility is not yet claimed; the receipt schema remains public.
The “Anchored to Base” rung shows green only once the receipt’s epoch root is attested on-chain — until then it honestly reads “pending.” No verified outside sales are reported; the public rail remains open for independent use.