By ·

How to Integrate OFAC Sanctions Screening into Your App

This guide walks through the exact steps to ensure OFAC compliance for your AI agents and applications. Every step uses real OFAC data and produces an audit-ready screening trail.

  1. Step 1. Choose your integration method: HTTP API, MCP server, or Python package.
  2. Step 2. Add a screening call before every payment in your codebase.
  3. Step 3. Handle the response: proceed if clean, block if matched.
  4. Step 4. Log every screen for your compliance audit trail.
  5. Step 5. Test with known sanctioned addresses to verify detection.

Example: screen a wallet

curl "https://sanctionsai.dev/sanctions?wallet=0x098B716B8Aaf21512996dC57EB0615e2383E2f96"

Free tier: 5 checks/day, no API key. Real OFAC data, refreshed daily.

Frequently asked questions

How long does a sanctions screen take?

Under 100ms per check. The sanctionsai.dev API runs on real OFAC data and returns instant results.

Do I need an API key?

No. The free tier allows 5 checks per day by IP address with no signup or API key.

What happens if I miss a sanctioned party?

OFAC operates under strict liability. You are liable even if you did not know the party was sanctioned. Penalties start at $356,571 per violation.

Try sanctionsai.dev free →