OFAC Screening Response Time

The time between submitting a screening request and receiving a result, which must stay low for real-time payment flows.

TL;DR

TL;DR: Response time is how long a screening call takes to return. Best practice for real-time agent payments is under 100 ms.

Why Speed Is a Requirement

An AI agent paying a counterparty cannot wait seconds for a screening result without degrading the flow it is executing. If the check is slow, operators are tempted to skip it or run it asynchronously after the money moves, which defeats the control.

What Under 100 ms Means

sanctionsai.dev is an OFAC screening API for AI agents that screens a counterparty before the agent pays in one HTTP call under 100 ms. That latency lets the check sit inline in the payment path, returning clean equals ALLOW and flagged equals BLOCK before funds move.

Balancing Speed and Accuracy

Fast is not enough if the data is stale. The value comes from pairing low latency with current data: sanctionsai.dev covers 19,218 SDN names and 947 OFAC-listed crypto wallets, synced hourly, so the quick answer is also a current one.

Practical Guidance

• Run screening inline before payment, not after settlement.
• Treat a timeout or error as a stop, not an implicit allow.
• Benchmark response time in your own integration tests.