Introduction
Leeri is a crypto AML screening API for exchangers, payment processors and iGaming operators. You send an address check or a transaction check and get back a verdict you can act on and defend: every finding names its source, and the verdict can be reproduced later exactly as it was issued.
What a verdict carries
Each check answers with one verdict object. It is made of these parts:
| Part | What it tells you |
|---|---|
| Score and band | A numeric score and a band: low, medium, high or severe. |
| Findings | Each finding states why the score moved. It links either the public source document it rests on, or a versioned methodology page that explains the rule. A third-party data source is never named: such a finding says source: "provider". |
| Exposure | How much of the address's flow is tied to risky categories, directly and through intermediaries. |
| Pin | The ruleset_version, label_snapshot_id and chain_height the verdict was derived at. The same pin always gives the same result, so a verdict can be re-derived later. |
| Evidence report | A PDF and JSON report for the verdict, included with every check, with a public page to confirm it is genuine and unaltered. |
If an upstream data source is unavailable, the check does not fail with a server error. It returns a partial verdict that says it is partial and why.
Synchronous or pending
A check answers in the same response when it can. When the answer needs more time, the response has status: "pending" and the same shape: poll the check until the status leaves pending, or register a webhook and receive a check.completed delivery once per finished check.
Sandbox and live
The environment is chosen by the key. An ak_sandbox_ key runs the real engine against your own data without consuming quota or balance, at a lower rate limit; an ak_live_ key is billed. Use sandbox keys while you build, then switch the key and nothing else. Plans and prices are on the pricing page.
Where to go next
- Quickstart: from a sandbox key to a verified webhook in five steps.
- How it works: the path of a check from request to pinned verdict.
- Methodology: how a score is built and what each rule detects.
- Integration guide: authentication, checks, polling, webhooks, limits, reports and errors.
- Migration from AMLBot: repoint three environment variables and keep your client.
- Telegram bot: check addresses and receive alerts in Telegram.
- API reference: every endpoint and schema, generated from the live contract.
- Changelog: customer-visible changes, newest first.
- Questions or a key request: hello@leeri.ai.