OFAC Screening SDK Documentation

SDK documentation is the technical reference for integrating screening: API references, code examples, guides, and troubleshooting.

TL;DR

TL;DR: OFAC screening SDK documentation is the technical material for integrating sanctions screening, including API references, code examples, integration guides, and troubleshooting notes.

What good documentation includes

The documentation should show the request and response shape, explain the ALLOW and BLOCK outcomes, and give copy paste code for common languages. It should also cover error handling and rate limits so an integration fails safely rather than silently skipping a screen, which would leave a payment unscreened.

Why it matters for agent payments

An agent integration lives or dies on how fast a developer can wire the screen into a payment flow. SanctionsAI ships an MCP server installed with pip install sanctions-mcp, and integrates with Claude Code, Cursor, Windsurf, LangChain, CrewAI, Eliza, and the OpenAI Agents SDK, so the screen drops into existing agent tooling instead of forcing a bespoke build.

Getting started quickly

The free tier, 5 checks per day with no signup and no key, lets a developer test the API in minutes. From there, one HTTP call under 100 ms returns ALLOW or BLOCK against 19,218 SDN names and 947 OFAC-listed crypto wallets, synced hourly, so the first integration is the same shape as the production one. Clear docs also cut the time between signing up and having a working screen in production, which is often where integration projects stall. Good examples do more for adoption than a long spec.