Addresses
Identification API
Know what is behind any address: exchange, issuer, bridge, mixer, privacy pool, scam or new contract classified by bytecode. Every label carries source and confidence.
Know who you are transacting with.
Read the docsAPIs & MCP
AuditKey APIs and MCP servers give your systems and AI agents risk scores, sanctions, stablecoin blocklists, community alerts and entity data, so they can screen, decide and escalate without waiting in a review queue.
Built for engineering teams at stablecoin issuers, fintechs, VASPs and compliance platforms.
Fraud is increasingly run by scripts, bots and AI. Fresh wallets appear on demand, funds split across chains and bridges, and scams are written by language models. A dashboard someone has to open and a queue someone has to clear answer too late. Compliance has to live inside the systems that move the money, and decide at the same speed.
Screen at mint, deposit, withdrawal and payout, by API, before the money moves. No exports, no second screen.
Your agents call AuditKey through MCP, clear routine cases on their own and escalate the rest with the evidence attached. You set which decisions an agent can take alone.
Every answer carries the labels, sources and confidence behind it, so an automated decision can be reviewed by an analyst or an examiner later.
| Legacy compliance | Agentic compliance with AuditKey |
|---|---|
| Batch reviews after settlement | Screening inside the transaction flow |
| An analyst queue for every alert | Agents clear routine cases; analysts handle exceptions |
| A dashboard someone has to open | Data delivered to systems and agents by API, webhooks and MCP |
| A black-box score | A score with the labels and sources behind it |
| Lists updated by hand | Sanctions, blocklists and community alerts updated as they change |

GET /v1/risk/{chain}/{address}
{
"address": "0x...",
"chain": "ethereum",
"risk": { "tier": "suspicious", "score": 78 },
"labels": [
{ "category": "stablecoin_blocklist", "source": "regional_issuer", "confidence": "deterministic" },
{ "category": "community_alert", "source": "cilada_cripto", "confidence": "reported" }
],
"exposure": { "direct": ["scam"], "indirect_hops": 2 }
}Addresses
Know what is behind any address: exchange, issuer, bridge, mixer, privacy pool, scam or new contract classified by bytecode. Every label carries source and confidence.
Know who you are transacting with.
Read the docsAddresses
One call returns risk tier, score and the evidence behind it, with direct and indirect exposure. Rules are configurable by your compliance officer.
Approve, hold or escalate a transfer.
GET /v1/risk/{chain}/{address}
Read the docsLists
Screen addresses and entities against OFAC SDN, EU and UN lists, updated as lists change.
Mandatory sanctions screening.
Read the docsLists
Every address frozen by major issuers, plus regional stablecoin blocklists in Brazil and Latin America available through our partnerships.
Block transfers to frozen wallets.
Read the docsLists
Addresses reported in scams by victims and partners, including Cilada Cripto, with the date and type of each report.
Catch regional fraud early.
Read the docsEntities
The VASP and fintech directory by API: who they are, where they are licensed and whether they support the Travel Rule.
Counterparty VASP due diligence.
Read the docsEntities
Screen individuals against sanctions and PEP (politically exposed person) lists and see their links to institutions in our directory.
Onboarding and enhanced due diligence.
Read the docsMCP (Model Context Protocol) servers expose our modules as tools any compatible agent can use. Your agents screen an address, trace funds or check a VASP (virtual asset service provider) in the middle of a workflow and act on the answer, under the same keys, scopes and audit log as our API.
A payments agent checks every withdrawal before approving it.
An investigation copilot follows funds and summarizes the path.
An onboarding agent screens a new counterparty.
A treasury agent checks the backing of a stablecoin before accepting it.
A deposit agent verifies funds that come from a privacy pool.
Each MCP server uses an API key limited to the tools you enable.
You decide which actions an agent can take alone and which need an analyst.
No MCP tool moves funds or changes your rules.
Every tool call by an agent is logged like an API call.
REST, webhooks and batch. Versioned JSON, keys scoped per environment, and one request for a list of addresses.
Ethereum and EVM-compatible chains, Tron, Solana and Bitcoin.
SOC 2 audit in progress. An audit log of every call.
Volume-based plans, scoped with each customer. Full reference in the docs.
How AuditKey APIs and MCP servers fit into the systems that move money.
AuditKey offers Identification, Risk, Sanctions, Stablecoin Blocklists, Community Alerts, Institutions and People APIs, plus MCP servers for KYT, Intelligence, Lists & Entities, Proof of Reserves and Privacy Pool Compliance.
The Model Context Protocol (MCP) is an open standard that lets AI agents call external tools. AuditKey MCP servers let your agents screen addresses, trace funds and check VASPs under the same keys and audit log as the API.
Agentic compliance means AI agents and automated systems that screen, decide and escalate compliance cases inside the transaction flow, with analysts reviewing exceptions. AuditKey supports it with APIs and MCP servers that return explainable answers, with the sources behind every label.
The Stablecoin Blocklists API covers addresses frozen by major global issuers, plus regional stablecoin blocklists in Brazil and Latin America available through our partnerships.
Yes. AuditKey APIs support batch requests for backfills and periodic reviews. Scope and volume are agreed during onboarding.
AuditKey APIs are priced by volume, scoped with each customer. Request API access to talk to our team.
AuditKey API access is granted after onboarding, with a test environment for your integration.