Let your AI agent spend money. Never let it move yours.

The model can ask. It can't pay.

Keeping the key away from the model is table stakes now — Turnkey, Privy and Coinbase do it inside their clouds. Two things set this apart: the checkpoint runs in your own Cloudflare account, not a vendor's, and every decision lands on a public hash-chain whose linkage anyone can re-walk — not a private compliance log. Row contents stay operator-attested; we mark prove-vs-trust. A compromised prompt has nothing to exploit.

See the gate refuse to be bypassed.

Ask for paid data with no payment. You get a 402 challenge back — proof the agent can request but cannot bypass the gate. Then pay on-chain, resend the hash, get the data once.

# 1. ask for trending tokens (no payment yet) — the gate answers with a challenge, not data:
curl -s -X POST https://ironbridge.foundation/api/pay/solvr/solvr_dex_trending

HTTP/1.1 402 Payment Required
{ "network":"base", "asset":"USDC", "price":"0.10",
  "receiver":"0x5Bb0a8A570F73eE0575043B8A9c33b28D6891680",
  "resend_with":"X-IB-Payment-Tx: <your base usdc tx hash>" }

# 2. pay 0.10 USDC on Base to the receiver, then resend with the tx hash:
curl -s -X POST https://ironbridge.foundation/api/pay/solvr/solvr_dex_trending \
  -H "X-IB-Payment-Tx: 0x<your-tx-hash>"
# → 200 OK · live data served once · payment verified on-chain · replay-guarded

Same gate, second live lane: CLERK court records

500M+ US federal court records, behind the exact same pay-then-prove gate. Pay $0.10 USDC, get real docket data back once, plus a receipt anyone can re-verify. The 402 gate is live and emits a real, re-verifiable receipt — proven end-to-end by an operator self-test ($0.10 USDC settled on-chain); no external customer has paid yet. The receipt honestly stamps clerk_tier:"demo_free" — today the upstream data runs on the free/demo tier; the 80%-discount paid tier flips on when our CLERK key is bound. What you re-verify on the receipt is exactly what the rail did.

# ask CLERK for a docket search (no payment yet) — same 402 challenge, same Safe receiver:
curl -s -X POST "https://ironbridge.foundation/api/pay/clerk/clerk_search?q=apple"

HTTP/1.1 402 Payment Required
{ "price_usdc":0.1, "receiver":"0x5Bb0a8A570F73eE0575043B8A9c33b28D6891680",
  "network":"base", "asset":"USDC" }

# pay 0.10 USDC on Base, resend with the hash → real court data + a re-verifiable receipt:
curl -s -X POST "https://ironbridge.foundation/api/pay/clerk/clerk_search?q=apple" \
  -H "X-IB-Payment-Tx: 0x<your-tx-hash>"
# → 200 OK · real federal docket data · category: Docket Footprint Check · LAW-25 receipt

Or wire it into your agent

Keyless MCP config — no token, no account. Published on npm — drop it in.

{ "mcpServers": { "ironbridge": {
    "command":"npx", "args":["-y","@ironbridgefoundation/ironbridge-mcp-server"] } } }

Four paid data tools — no key, pay per call

Or put the gate on your app — GITLAWB rails

Built something in a vibe-code tool and want it to take real money safely? Add two lines. Your app now charges a stranger, and the gate refuses unpaid or forged calls today (proven live); per-action spend-caps are built and ship in IronBridge-in-a-Box, not yet exercised by an external payment. It emits a re-verifiable receipt — your code and your money never route through us. You keep your revenue; the rails take a small fee on-chain at pay time. (Live — the 402 gate and on-chain split run today, proven by operator self-test; no external customer has paid through it yet.)

import { charge } from "@ironbridge/gitlawb";   // 1. keyless — SDK built, not yet on npm (request access)
// 2. point payments at YOUR wallet (env or option) — never defaults to us
const pay = charge({ price: "0.10", receiver: "0xYourWallet", label: "lookup" });

app.post("/lookup", pay, async (req,res)=>{           // 3. wrap your route
  res.json(await myAgent.run(req.body));     // stranger paid → bounded run → receipt minted
});

A stranger hits your route → 402, pay $0.10 USDC on Base → pays → your app serves once → a LAW-25 receipt is minted that the buyer re-verifies themselves. On a real call the split is visible and on-chain: 95.5% to your wallet · a flat 4.5% rails fee — nothing hidden (the split is enforced on-chain at pay time; not yet exercised by an external payment). The bounded signer (un-drainable in test) + audit chain you couldn't build alone, in two lines.

The GitLawb Forge — build an app free, then bolt the rails on

Open the Forge and chat with AI to build a real Vite + React app, watch it preview live, and publish it to your own gitlawb.app subdomain — free, no signup. Then add the two lines above and the same app can take a paid call with a re-verifiable receipt. (The Forge builds + publishes free today; the charge() pay-rail is live today — the 402 gate and split run now; no stranger has paid through it yet.)

A self-hosted deterministic checkpoint beneath your agent.

You already gave your agent reach and a wallet. IronBridge is a self-hosted deterministic checkpoint below your agent's model that writes a re-walkable audit chain — the gate refuses unpaid or forged calls today (proven live), and per-action spend-caps are built and ship in IronBridge-in-a-Box, not yet exercised by an external payment. It composes with the stack you already use; it doesn't replace it.

# re-walk the head + most-recent window — confirm continuity yourself
curl -s https://ironbridge.foundation/api/law25/verify
→ { "window": { "continuity_ok": true }, "head": … }