Compliance APIs for developers

CompliAPI is a small set of screening primitives that share one API token, one quota and one request log: direct checks against the US Treasury OFAC SDN list, location signals for jurisdiction rules, and an MCP server that hands the same capabilities to AI agents. Integrate the pieces your product needs.

Sanctions screening

OFAC API — screen against the official SDN list

Check identifiers against the official US Treasury OFAC Specially Designated Nationals (SDN) list, refreshed every 15 minutes, with a bearer token and a GET request. Every match links to the official OFAC source record.

Explore

Wallet screening API for crypto compliance

Submit an onchain address — or an ENS name — and get back a structured verdict against OFAC and every other enabled sanctions, crime and risk list, with the designated entity and official source record on every match.

Explore

Access controls

Crypto geofencing API

Geolocate the calling client — or any IP address — and get back city, region, country, and whether that country is under OFAC sanctions programs. Your application applies the policy.

Explore

VPN Detection API for Sanctions Compliance

Check whether the calling client — or any IP address — is connecting through a VPN before you trust its location. A clear true / false / unknown signal that keeps geo-blocking effective for sanctions compliance.

Explore

AI infrastructure

OFAC MCP server for AI agents

Every CompliAPI screening capability is exposed as a tool over the Model Context Protocol, so AI agents and assistants can run OFAC checks directly — same API token, same quota, same request log as the REST API.

Explore

How the pieces fit together

The sanctions-screening APIs answer questions about identifiers: does this wallet address, email, website, government ID or country appear in OFAC data? The access-control APIs answer questions about sessions: where does this request appear to come from, and is it arriving over a VPN? Most products combine both — screening identifiers at onboarding and before funds move, and applying jurisdiction rules per session. The MCP server exposes all of it to AI agents with the same credentials, so screening works wherever your workflow runs.

Everything is a simple authenticated GET request documented in the technical documentation, and you can get a free API key to try it against live data.

Explore by use case

See how these capabilities combine for specific products and teams.

OFAC compliance API for DeFi

Read the use case

Sanctions screening for stablecoin payments

Read the use case

Sanctions screening for crypto exchanges

Read the use case

Compliance tools for AI agents

Read the use case

All use cases →

Add compliance screening to your application

Get a free API key and make your first request in minutes.

Get your free API key Read the documentation

14-day free trial. No credit card required.