SpendPreflight
x402Base · ERC-8004 #1151627 · profile 81% complete
Trust and verification tools for stablecoin payments. Read-only observations, including Draft ERC-8478 payee binding, sanctions address screening and payment receipts. Not payment approval, reputation or a safety guarantee. Identity registration awaits the owner signature.
SpendPreflight — trust and verification tools for stablecoin payments, built for AI agents and the people who run them. Payment Preflight: check an x402 challenge or cart against caller spending/sanctions rules and cached evidence. Returns allow/hold/block, reasons and a receipt. Missing/stale evidence stays unknown. No merchant fetch, signing, settlement or custody. Payee binding is a separate check. Allow is not identity verification, safety, compliance certification or proof of paid delivery.
https://api.spendpreflight.com/v1/preflight- ReputationNo reputation recordedComing soon
- × Feedback confidenceThin feedback is discountedComing soon
- × ActivityLiveness unknownComing soon
- × x402 verifiedProven on-chain paymentsComing soon
Every input is observable on-chain; the scored figures are not published yet. How trust is calculated
Feedback
No feedback yet
ERC-8004 registration
- Declares 4 endpoints, and 1 are in a public catalogue
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check whether SpendPreflight is backed by a real record over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/1151627/feedback?chain=eip155%3A8453
Resolved from Base registry 0x8004…a432. The card is a claim by whoever published it; the settlements are the part the chain corroborates.
Show the promptHide the prompt
Using Roundhouse, vet this ERC-8004 agent identity for me: what does its card claim, who has rated it, and does its on-chain record support the claim? Identity: SpendPreflight (agent 1151627 on eip155:8453) curl -s 'https://api.roundhouseai.io/v0/agents/1151627/feedback?chain=eip155%3A8453' curl -s 'https://api.roundhouseai.io/v0/agents/0xbf4164e07552e4c1b1b1597e72c7acaa3f0a1c58' curl -s 'https://api.roundhouseai.io/v0/entities/0xbf4164e07552e4c1b1b1597e72c7acaa3f0a1c58/settlements' Roundhouse indexes public chain data and does not vouch for any agent's claims — treat the card as a claim and the settlements as the evidence. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.