Available Tools - CompliAPI

Every tool returns the same JSON envelope as its REST counterpart, is metered against your organization’s quota, and (without a token) accepts x402 micropayments per call.

Screening tools

All five take the value to screen plus an optional lists argument — a comma-separated set of source list slugs to narrow the scope (unknown slugs error). Responses match the REST /screen/* envelope: sanctioned is true only for government sanctions hits, flagged covers crime-intelligence and risk-exposure hits too, and matches names the list behind each hit.

Tool	Arguments	Screens
`screen_crypto_address`	`address`, `lists?`	A crypto address on any chain; dotted names (e.g. `vitalik.eth`) are ENS-resolved first
`screen_email`	`email`, `lists?`	An email address
`screen_website`	`website`, `lists?`	A website or domain
`screen_government_id`	`government_id`, `lists?`	A government-issued ID (passport, tax ID, …), fuzzy-matched
`screen_country`	`country`, `lists?`	A country or region’s sanctions designations (OFAC-curated today)

Network tools

Tool	Arguments	Returns
`detect_vpn`	`ip_address`	Whether the IP is using a VPN — same shape as `/vpn`
`geolocate_ip`	`ip_address`	The IP’s location, flagging whether it is in a sanctioned country — same shape as `/geo`

Errors

Over-quota calls return a tool error (or, with x402 enabled, a payment challenge as the error result’s structured content). Invalid arguments — an unknown lists slug, a malformed IP — also come back as tool errors rather than protocol failures, so agents can read the message and retry.

​Screening tools

​Network tools

​Errors

Screening tools

Network tools

Errors