{ "schemaVersion": "ready-scan.agent-evidence.v1", "protocolVersion": "ready-scan.agent-return.v1", "entity": { "id": "urn:readyscan:entity:compliapi-q141485323", "slug": "compliapi-q141485323", "name": "CompliAPI", "lifecycle": "active", "revision": "fnv1a64:7e89c847fe47b0b2" }, "self": "https://readyscan.ai/api/v1/ai-search/entities/compliapi-q141485323/evidence", "evidenceRevision": "fnv1a64:13a1eec3b249efb2", "asOf": "2026-10-27", "ownershipState": "public_sourced_unclaimed", "provenance": { "snapshotId": "compliapi-q141485323-content-da2fa6b38ddb1c12-snapshot", "sourceId": "ready-scan-subjects", "sourceRecordId": "Q141485323", "sourceRevisionId": "Q141485323:content:086e8da14c2f2245", "sourceContentHash": "fnv1a64:4cb98410a8847475", "recordRevisionId": "Q141485323:content:086e8da14c2f2245", "recordContentHash": "fnv1a64:e420384f93dbb2e5", "sourceCanonicalUrl": "https://compliapi.com/", "sourceModifiedAt": "2026-10-27T16:19:36.859Z", "observedOn": "2026-10-27", "permission": { "basis": "public_information", "evidenceUrl": "https://compliapi.com/" }, "attributionUrl": "https://compliapi.com/" }, "assertions": [ { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-88b576af17e1581fd647", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-88b576af17e1581fd647", "claimText": "“Real-time OFAC and global sanctions screening API: screen crypto addresses, emails, websites, government IDs, and countries against the US Treasury SDN list and 10+ sanctions, crime, and risk lists, with VPN detection and IP geolocation.”", "position": "supports", "sources": [ { "sourceId": "source-record", "title": "CompliAPI website", "publisher": "compliapi.com", "url": "https://compliapi.com/", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-20d8c723438bf162a851", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-20d8c723438bf162a851", "claimText": "“No. Mobile geofencing SDKs (Android's GeofencingClient, Apple Core Location regions, and location-platform SDKs) fire events when a device enters or leaves a geographic area, using the device's own GPS.”", "position": "supports", "sources": [ { "sourceId": "source-49fef611b5ff89d1", "title": "compliapi.com/solutions/crypto-geofencing-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/crypto-geofencing-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-f73451fc92827b8515c1", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-f73451fc92827b8515c1", "claimText": "“The API is a plain authenticated GET request, so it works from any language without an SDK — the cURL, Python and Node examples above are complete. For AI-agent stacks, the same geolocation is exposed as a tool on CompliAPI's MCP server, alongside VPN detection and the screening tools.”", "position": "supports", "sources": [ { "sourceId": "source-49fef611b5ff89d1", "title": "compliapi.com/solutions/crypto-geofencing-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/crypto-geofencing-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-439aa9d0df7013e5f0f1", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-439aa9d0df7013e5f0f1", "claimText": "“Yes. A free API key includes 1,000 requests per month across all endpoints, geolocation included, and requests can also be paid per call with x402 USDC micropayments without an account. Paid plans raise the monthly quota.”", "position": "supports", "sources": [ { "sourceId": "source-49fef611b5ff89d1", "title": "compliapi.com/solutions/crypto-geofencing-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/crypto-geofencing-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-dec5128193c5bcec40f3", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-dec5128193c5bcec40f3", "claimText": "“Countries and regions under OFAC sanctions programs, curated by CompliAPI across comprehensive, targeted and military designations. Each flag includes a source_url so you can review the underlying program.”", "position": "supports", "sources": [ { "sourceId": "source-49fef611b5ff89d1", "title": "compliapi.com/solutions/crypto-geofencing-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/crypto-geofencing-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-f7244af490529a2e15e0", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-f7244af490529a2e15e0", "claimText": "“Yes — responses include city and region alongside country, so your application can implement rules such as special handling for New York State users.”", "position": "supports", "sources": [ { "sourceId": "source-49fef611b5ff89d1", "title": "compliapi.com/solutions/crypto-geofencing-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/crypto-geofencing-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-e9e723d70ab1b916174e", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-e9e723d70ab1b916174e", "claimText": "“No — OFAC itself publishes the SDN list as downloadable data files and a public search website, not as an API.”", "position": "supports", "sources": [ { "sourceId": "source-e2399d3bd6679f8f", "title": "compliapi.com/solutions/ofac-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-afd552dbf5570dcdd2c1", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-afd552dbf5570dcdd2c1", "claimText": "“To find out, before you deal with a party, whether an identifier belongs to someone on OFAC's SDN or Non-SDN lists or sits in a jurisdiction under an OFAC country program.”", "position": "supports", "sources": [ { "sourceId": "source-e2399d3bd6679f8f", "title": "compliapi.com/solutions/ofac-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-1f6f153cdfe8c0f4c427", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-1f6f153cdfe8c0f4c427", "claimText": "“Yes. Screening covers the SDN and Blocked Persons list, OFAC's Non-SDN Consolidated Sanctions List (SSI, NS-CMIC, CAPTA and similar — same publication stream, ingested every 15 minutes), and OFAC's country-level sanctions programs. Every call also checks official lists from other jurisdictions — the UK, EU, France and Japan among them — with each match naming the list that produced it.”", "position": "supports", "sources": [ { "sourceId": "source-e2399d3bd6679f8f", "title": "compliapi.com/solutions/ofac-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-fab0a3494025affcb068", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-fab0a3494025affcb068", "claimText": "“Yes. GET /api/v1/screen/crypto/{address} checks any address format OFAC publishes in SDN records — ETH, BTC, XMR, USDT and more — and ENS names are resolved on Ethereum mainnet before screening. The wallet screening page covers chain and coverage details.”", "position": "supports", "sources": [ { "sourceId": "source-e2399d3bd6679f8f", "title": "compliapi.com/solutions/ofac-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-2b41c2dd0d3578b729bc", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-2b41c2dd0d3578b729bc", "claimText": "“There are open-source SDN parsers and self-hosted search projects on GitHub, and they are a reasonable starting point if you want to own the pipeline.”", "position": "supports", "sources": [ { "sourceId": "source-e2399d3bd6679f8f", "title": "compliapi.com/solutions/ofac-api", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-api", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-811f3beaae8e44deef3f", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-811f3beaae8e44deef3f", "claimText": "“Yes. Authenticate with your existing CompliAPI API token as a bearer header. Tool calls are metered against your organization's quota exactly like REST requests.”", "position": "supports", "sources": [ { "sourceId": "source-2f257786a836fcfd", "title": "compliapi.com/solutions/ofac-mcp-server", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-mcp-server", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-b998ef33b8b3e281f4f7", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-b998ef33b8b3e281f4f7", "claimText": "“screen_crypto_address, screen_email, screen_website, screen_government_id, screen_country, screen_pep, detect_vpn and geolocate_ip — the full set of CompliAPI screening capabilities.”", "position": "supports", "sources": [ { "sourceId": "source-2f257786a836fcfd", "title": "compliapi.com/solutions/ofac-mcp-server", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-mcp-server", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-9e1a7fecfcc95991c17d", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-9e1a7fecfcc95991c17d", "claimText": "“Any client that supports remote MCP servers over streamable HTTP. Add the server URL and an Authorization header to the client's MCP configuration.”", "position": "supports", "sources": [ { "sourceId": "source-2f257786a836fcfd", "title": "compliapi.com/solutions/ofac-mcp-server", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-mcp-server", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-61283f502116d4442c5c", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-61283f502116d4442c5c", "claimText": "“No. The MCP tools call the same screening logic and the same OFAC SDN data, refreshed every 15 minutes, as the REST endpoints.”", "position": "supports", "sources": [ { "sourceId": "source-2f257786a836fcfd", "title": "compliapi.com/solutions/ofac-mcp-server", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-mcp-server", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] }, { "evidenceId": "ev-content-native-digital-agencies-6b096a69898fd728-a-3c198b834a63451d5b25", "claimId": "content-native-digital-agencies-6b096a69898fd728-a-3c198b834a63451d5b25", "claimText": "“For critical flows, most teams also enforce checks deterministically in application code — the REST API exposes the same data with the same credentials, so the backstop is one request away.”", "position": "supports", "sources": [ { "sourceId": "source-2f257786a836fcfd", "title": "compliapi.com/solutions/ofac-mcp-server", "publisher": "compliapi.com", "url": "https://compliapi.com/solutions/ofac-mcp-server", "accessedOn": "2026-10-27", "sourceRevision": "Q141485323:content:086e8da14c2f2245" } ] } ], "contradictionState": "none_recorded", "ambiguityState": "none_recorded", "relations": { "discovery": "https://readyscan.ai/api/v1/ai-search/discovery", "evidence": "https://readyscan.ai/api/v1/ai-search/entities/compliapi-q141485323/evidence" }, "limitations": [ "This document connects published company information to its retained source references. Unmatched IDs remain unknown; reading it does not refresh the sources." ] }