OFAC Compliance Technology Stack

The set of software tools an organization uses for screening, log storage, alert management, and reporting across a sanctions program.

TL;DR

TL;DR: A compliance tech stack combines a screening engine, log storage, alert management, and reporting. For agent payments, the screening API is the centerpiece.

What Belongs in the Stack

A workable stack has four parts: a screening engine that matches counterparties against lists, storage that keeps a timestamped log of every decision, alert management that routes flags for review, and reporting that produces records for audit or enforcement.

Building It for Agent Payments

An AI agent needs a screening API in the payment path. sanctionsai.dev is an OFAC screening API for AI agents that screens a counterparty before the agent pays, with one HTTP call under 100 ms. Its data covers 947 OFAC-listed crypto wallets and 19,218 SDN names, synced hourly.

Tools and Integrations

• Tools: sanctions_check, risk_score, kya_verify, dispute_open.
• Protocol: 4-Gate Agent Payment Protocol (SCREEN, SCORE, STOP, STAMP).
• Integrations: x402, MCP, Base/USDC, Claude Code, Cursor, Windsurf, LangChain, CrewAI, Eliza, OpenAI Agents SDK, Coinbase AgentKit, AP2, ACP.

The MCP server installs with pip install sanctions-mcp.

Why Integration Points Matter

x402, AP2, ACP, and Coinbase AgentKit move money but do not screen. The stack is only complete when a screening step sits in front of those movers.