Block sanctioned wallets in AI agents
Enforce OFAC-listed wallet screening in the payment path, with clear limits on what a match means.
Keep the check next to the signer
A model can overlook a tool recommendation. Put the check in the payment hook that runs before a wallet signs. With screen_sanctions enabled, preflight returns block when the selected payTo matches an address in its current OFAC SDN index. The caller must enforce that decision.
Understand the evidence
The index contains digital-currency addresses listed in OFAC SDN remarks, plus names and aliases. This is not blockchain tracing or a list of every wallet controlled by a sanctioned party. A missing match does not establish that a payee is safe. Name matches need human review; exact names and possible names have different decision handling.
Check data freshness
Read /health for sdn_entries and sdn_as_of. Daily refresh is monitored, but a timestamp does not guarantee completeness. Keep a fail-closed policy when screening is unavailable and review suspected matches before acting.
Use the live interface
GET /v1/check costs $0.01; POST /v1/preflight costs $0.02. Paid calls use Base USDC over x402. No SpendPreflight account, API key or OAuth is required. The shared trial is three HTTP/MCP calls per IP per UTC day. The response includes flags and evidence; it cannot replace your legal or compliance obligations.
Connect your payment client
Tested fetch, axios, Vercel and OpenAI Agents examples · Live default rules · OpenAPI
We operate SpendPreflight. Scout discovery and seller monitoring remain staging-only; these guides describe the live check/preflight service.
Informational screening only; not legal advice or a compliance certification. Trust and limitations · Privacy