They sell investigations to compliance teams. We sell decisions to developers.

Clearlist screens addresses, names, countries and transactions against government sanctions lists and public chain labels, and answers with allow, review or block, plus the reasons and the evidence. Solana, Ethereum, Base, BNB Chain, Robinhood Chain, every other EVM chain and 12 more. One endpoint. Five minutes to the first call.

Free: unlimited address checks, 1,000 metered screens a month, unlimited test screens. No card, no call.

Decision
dec_8f3k2m9q1x7p4v6n0b5c2
31 ms, policy v3
06 Oct 2026 14:02
Address on Ethereum
0x098b716b…383e2f96
block
  1. Sanctioned address
    critical address.sanctioned

    The address 0x098b…2f96 appears on the OFAC SDN list under the DPRK3 program (Lazarus Group), batch published 2026-09-30.

    List
    OFAC SDN
    Entry
    LAZARUS GROUP OFAC_SDN:27307
    Program
    DPRK3
    List batch
    batch_2026_09_30_sdn
  2. Direct exposure
    high exposure.direct

    2 of 184 scanned transactions interact directly with a sanctioned counterparty (hop 1).

    Scanned
    184 transactions on Ethereum
    Hop 1
    0xa0e1c8…c20e4b outbound, 2 transactions, listed as OFAC_SDN:27307
Screened against
  • OFAC SDN 30 Sept 2026
  • OFAC Consolidated 30 Sept 2026
  • EU Financial Sanctions 03 Oct 2026
  • UK OFSI 02 Oct 2026
  • UN Security Council 28 Sept 2026
The same decision as JSON
{
  "id": "dec_8f3k2m9q1x7p4v6n0b5c2",
  "org_id": "org_demo",
  "outcome": "block",
  "reasons": [
    {
      "code": "address.sanctioned",
      "severity": "critical",
      "summary": "The address 0x098b…2f96 appears on the OFAC SDN list under the DPRK3 program (Lazarus Group), batch published 2026-09-30.",
      "evidence": {
        "list": "OFAC_SDN",
        "batch_id": "batch_2026_09_30_sdn",
        "entity_id": "OFAC_SDN:27307",
        "primary_name": "LAZARUS GROUP",
        "programs": [
          "DPRK3"
        ],
        "asset_code": "ETH",
        "address": "0x098b716b8aaf21512996dc57eb0615e2383e2f96",
        "source_url": "https://sanctionssearch.ofac.treas.gov/Details.aspx?id=27307"
      }
    },
    {
      "code": "exposure.direct",
      "severity": "high",
      "summary": "2 of 184 scanned transactions interact directly with a sanctioned counterparty (hop 1).",
      "evidence": {
        "chain": "ethereum",
        "provider": "etherscan",
        "scanned_txs": 184,
        "hits": [
          {
            "counterparty": "0xa0e1c89ef1a489c9c7de96311ed5ce5d32c20e4b",
            "hop": 1,
            "direction": "out",
            "tx_count": 2,
            "via": "OFAC_SDN:27307"
          }
        ]
      }
    }
  ],
  "subject": {
    "type": "address",
    "address": "0x098b716b8aaf21512996dc57eb0615e2383e2f96",
    "chain": "ethereum"
  },
  "matches": {
    "addresses": [
      {
        "address": "0x098b716b8aaf21512996dc57eb0615e2383e2f96",
        "chain": "ethereum",
        "list": "OFAC_SDN",
        "batch_id": "batch_2026_09_30_sdn",
        "entity_id": "OFAC_SDN:27307",
        "primary_name": "LAZARUS GROUP",
        "programs": [
          "DPRK3"
        ]
      }
    ],
    "names": [],
    "labels": []
  },
  "exposure": [
    {
      "status": "ok",
      "chain": "ethereum",
      "address": "0x098b716b8aaf21512996dc57eb0615e2383e2f96",
      "provider": "etherscan",
      "scanned_txs": 184,
      "counterparties": 61,
      "hits": [
        {
          "counterparty": "0xa0e1c89ef1a489c9c7de96311ed5ce5d32c20e4b",
          "hop": 1,
          "direction": "out",
          "tx_count": 2,
          "first_seen": "2026-08-14T09:12:00Z",
          "last_seen": "2026-09-02T17:40:00Z",
          "via": {
            "address": "0xa0e1c89ef1a489c9c7de96311ed5ce5d32c20e4b",
            "chain": "ethereum",
            "list": "OFAC_SDN",
            "batch_id": "batch_2026_09_30_sdn",
            "entity_id": "OFAC_SDN:27307",
            "primary_name": "LAZARUS GROUP",
            "programs": [
              "DPRK3"
            ]
          }
        }
      ],
      "computed_at": "2026-10-06T14:02:11Z",
      "cached": false
    }
  ],
  "lists": {
    "OFAC_SDN": {
      "batch_id": "batch_2026_09_30_sdn",
      "published_at": "2026-09-30T00:00:00Z",
      "fetched_at": "2026-10-06T06:00:03Z",
      "entry_count": 17842
    },
    "OFAC_CONS": {
      "batch_id": "batch_2026_09_30_cons",
      "published_at": "2026-09-30T00:00:00Z",
      "fetched_at": "2026-10-06T06:00:05Z",
      "entry_count": 512
    },
    "EU_FSF": {
      "batch_id": "batch_2026_10_03_eu",
      "published_at": "2026-10-03T00:00:00Z",
      "fetched_at": "2026-10-06T06:00:09Z",
      "entry_count": 5231
    },
    "UK_OFSI": {
      "batch_id": "batch_2026_10_02_uk",
      "published_at": "2026-10-02T00:00:00Z",
      "fetched_at": "2026-10-06T06:00:12Z",
      "entry_count": 4790
    },
    "UN_SC": {
      "batch_id": "batch_2026_09_28_un",
      "published_at": "2026-09-28T00:00:00Z",
      "fetched_at": "2026-10-06T06:00:14Z",
      "entry_count": 1123
    }
  },
  "policy_version": 3,
  "user_message": "We can't process this transaction. Contact support with reference dec_8f3k2m9q1x7p4v6n0b5c2.",
  "latency_ms": 31,
  "created_at": "2026-10-06T14:02:11Z",
  "idempotency_key": "withdrawal_91f2",
  "metadata": {
    "user_id": "usr_4421",
    "flow": "withdrawal"
  }
}

A real decision on the Ronin bridge exploit address that OFAC attributes to the Lazarus Group. Public record; the source link opens the SDN entry.

The whole integration is this request

One POST with the subject. The response above comes back in tens of milliseconds for addresses; exposure runs inside a budget and never blocks the answer.

POST /v1/screen
curl https://clearlist.xyz/api/v1/screen \
  -H "Authorization: Bearer cl_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": {
      "type": "address",
      "address": "0x098b716b8aaf21512996dc57eb0615e2383e2f96"
    },
    "metadata": { "user_id": "usr_4421", "flow": "withdrawal" }
  }'

A background check for money

Apps that move money, including crypto apps, are required to make sure they are not dealing with sanctioned people, companies or wallets. Clearlist does that check for them, instantly, and keeps the proof.

  1. Step 1

    Your app asks

    Before a user signs up or money moves, the app sends us one thing to check: a wallet address, a person's name, a country, or a whole transaction.

  2. Step 2

    We check everywhere that matters

    Every official government sanctions list (US, EU, UK, UN), public records of hacker, mixer and scam wallets, and who that wallet has actually transacted with.

  3. Step 3

    You get an answer you can act on

    In well under a second: allow, review, or block. With the reason in plain English and the evidence attached, so you can show it to a user, a bank, or a regulator.

allow

Nothing matched. The app lets the sign-up or payment through. This is the answer for almost everyone.

review

Something looks like a match but is not certain, for example a common name. A human takes a look; one click clears or confirms it.

block

A definite match: a listed wallet, or a name confirmed by a date of birth or ID. The app stops the transaction and has the record to prove why.

Who it is for

Crypto wallets, stablecoin payment apps, exchanges, cash-in and cash-out ramps, marketplaces, launchpads, fintechs adding crypto, and new blockchains that want every app in their ecosystem covered from day one. Anyone whose bank or partner is about to ask “what do you do about sanctions?”

What you get beyond the check

  • A permanent record of every decision, exportable, to hand to a bank or auditor.
  • Ongoing monitoring: if one of your users gets listed next month, you are told the same day.
  • A one-page attestation describing your screening controls, with a link you can share.

Questions people ask

What is a sanctions list?
Governments publish lists of people, companies and, increasingly, crypto wallets that it is illegal to do business with: terrorist financiers, North Korean hacking groups, sanctioned banks, drug cartels. The US list alone has about 19,000 entries and over 1,000 wallet addresses.
Why does a small crypto app need this?
Because its bank, payment partner, ramp provider, or app store will ask what it does about sanctions, and "nothing" ends the relationship. Regulators also fine companies that move money for listed parties, whether or not they knew.
Do you need a licence to provide this?
No. No regulator licenses screening vendors, and the large providers do not hold one either. What makes screening credible is pulling from the official sources, keeping a dated record of every decision, and being able to show both. That is what Clearlist does.
Is this legal advice?
No. Clearlist tells you what was screened, what it matched, and why. Whether a business is compliant depends on its whole program. The attestation page and the Compliance Pack describe the controls in operation; they are not an opinion on compliance.
Where does the data come from?
Directly from the publishers: the US Treasury (OFAC), the European Union, the UK's OFSI, and the United Nations, refreshed every few hours and versioned. Plus public, cited records of hacks, mixers and scams. No resold third-party datasets.
What does it cost?
Address checks are free and unlimited on every plan, plus 1,000 name, country and transaction screens a month while you build. $299 a month for a production app, $1,500 a month for a company with a bank or auditor asking, which includes the Compliance Pack. Chains and foundations can sponsor coverage for every app in their ecosystem, from $50,000 a year.
How is this different from Chainalysis, Elliptic or TRM?
They sell investigation tools to compliance teams at banks and large exchanges: enterprise contracts, sales calls, weeks of integration, and deep attribution graphs we do not try to match. We sell decisions to developers: self-serve, public pricing, explainable answers, first check in five minutes. The comparison page goes row by row, and pricing shows what each plan includes.

Want to send this to someone? The plain-English page stands on its own.

Built for the four things incumbents lose small customers on

Self-serve

Sign up, get a key, make the first call. Public pricing, a free tier, and no discovery call. Five minutes is the whole onboarding.

Explainable

Every decision is allow, review or block, with a list of reasons. Each reason has a one-sentence summary and the evidence behind it: which list, which entry, which batch, which counterparty, which hop. No risk scores to interpret.

False positives are yours to control

A policy you edit, an allowlist you own, and a review queue with one-click clear or confirm. A name alone never blocks; it needs a corroborating identifier.

Evidence, not vibes

Decisions are append-only and record the exact list versions used. Export the evidence file for any decision, or print the attestation that describes your program.

Solana, 32 EVM chains and 12 more. Screening on all 45, counterparty exposure on 32.

Solana
Yes
EVM
32
All chains
45
With exposure
32

Solana and the EVM family get the full treatment: lists, labels and who the wallet has transacted with. Every other chain is screened against the government lists the day an address is listed. A new chain can be added the week it launches. Foundations can sponsor coverage for every app in their ecosystem; see pricing. The registry is public at GET /api/v1/chains.

Screening: every chain

Is this exact address on a government sanctions list, or in a public label set for mixers, hacks, scams, darknet markets and ransomware? Designated addresses are strings, so this works on any chain, including ones that launched yesterday. Government lists are matched on every chain; public labels are matched on the chains where a label source exists.

Exposure: 32 chains

Who has this address transacted with? One hop today, two hops reported as information. Runs on Solana through Helius or any Solana RPC, and on every Etherscan-indexed EVM chain, from Ethereum, Base, BNB Chain and Robinhood Chain to Monad and HyperEVM, through the Etherscan v2 API. Bitcoin, Tron, the UTXO chains, Monero and XRP are screening-only for now; exposure arrives as providers are added.

Featured chains

Screening and counterparty exposure Screening only
  • Solana
    Solana/screening + exposure
  • Ethereum
    EVM 1/screening + exposure
  • Base
    EVM 8453/screening + exposure
  • BNB Smart Chain
    EVM 56/screening + exposure
  • Robinhood Chain
    EVM 4663/screening + exposure
  • Arbitrum One
    EVM 42161/screening + exposure
  • OP Mainnet
    EVM 10/screening + exposure
  • Polygon
    EVM 137/screening + exposure
  • Avalanche C-Chain
    EVM 43114/screening + exposure
  • Arc
    EVM 5042/screening + exposure
  • Bitcoin
    Bitcoin/screening
  • Tron
    Tron/screening
And 33 more: 23 EVM chains with exposure (Ethereum Classic screening-only), plus 10 screening-only chains
ChainidFamilyScreeningExposure
LinealineaEVM59144Lists + labelsEtherscan v2
ScrollscrollEVM534352Lists + labelsEtherscan v2
ZKsync ErazksyncEVM324Lists + labelsEtherscan v2
BlastblastEVM81457Lists + labelsEtherscan v2
MantlemantleEVM5000Lists + labelsEtherscan v2
GnosisgnosisEVM100Lists + labelsEtherscan v2
CeloceloEVM42220Lists + labelsEtherscan v2
CronoscronosEVM25Lists + labelsEtherscan v2
SonicsonicEVM146Lists + labelsEtherscan v2
BerachainberachainEVM80094Lists + labelsEtherscan v2
UnichainunichainEVM130Lists + labelsEtherscan v2
World ChainworldchainEVM480Lists + labelsEtherscan v2
AbstractabstractEVM2741Lists + labelsEtherscan v2
ApeChainapechainEVM33139Lists + labelsEtherscan v2
opBNBopbnbEVM204Lists + labelsEtherscan v2
Sei EVMseiEVM1329Lists + labelsEtherscan v2
HyperEVMhyperevmEVM999Lists + labelsEtherscan v2
MonadmonadEVM143Lists + labelsEtherscan v2
Polygon zkEVMpolygon-zkevmEVM1101Lists + labelsEtherscan v2
FraxtalfraxtalEVM252Lists + labelsEtherscan v2
TaikotaikoEVM167000Lists + labelsEtherscan v2
MoonbeammoonbeamEVM1284Lists + labelsEtherscan v2
Ethereum Classicethereum-classicEVMLists + labelsNot yet
LitecoinlitecoinUTXOLists + labelsNot yet
Bitcoin Cashbitcoin-cashUTXOLists + labelsNot yet
Bitcoin SVbitcoin-svUTXOLists + labelsNot yet
Bitcoin Goldbitcoin-goldUTXOLists + labelsNot yet
DogecoindogecoinUTXOLists + labelsNot yet
DashdashUTXOLists + labelsNot yet
ZcashzcashUTXOLists + labelsNot yet
VergevergeUTXOLists + labelsNot yet
MoneromoneroOtherLists + labelsNot yet
XRP LedgerxrpOtherLists + labelsNot yet

Who it is for

Six kinds of team, each with a moment when screening stops being optional. What they screen and which parts of Clearlist carry the load.

Stablecoin payment apps and non-custodial wallets

The trigger
Your ramp provider, card issuer or bank partner asks for your sanctions program before they will move the first dollar.
What they screen
Sign-ups, Sends, Claims and link payments, Deposits.
What they use
  • Address screening on every chain
  • Counterparty exposure on Solana, Base, BNB Chain, Robinhood Chain and every EVM chain
  • Continuous monitoring with webhooks
  • Compliance Pack and attestation for the partner review

Exchanges and cash on/off ramps

The trigger
You hold customer funds, so a regulator or banking partner expects screening at onboarding and on every withdrawal, with records.
What they screen
Onboarding names, Deposit addresses, Withdrawal addresses, Countries of residence.
What they use
  • Name screening with corroboration
  • Transaction subjects (both sides in one call)
  • Review queue for analysts
  • Evidence export per decision

DeFi frontends, launchpads and NFT marketplaces

The trigger
A sanctioned address connects to your interface and you have no record of having checked. Frontends have been the enforcement target before.
What they screen
Wallet connects, Mints and launches, Trades routed through your UI.
What they use
  • Address screening with public labels (mixers, hacks)
  • Allowlist for known contracts and routers
  • Policy per label category
  • Idempotent screens per session

Fintechs and neobanks adding crypto

The trigger
Your bank partner already requires name and country screening; now you need wallet addresses screened too, with evidence in one format.
What they screen
Customer names with DOB and nationality, Countries, Linked external wallets, Outbound crypto transfers.
What they use
  • Name plus address screening in one API
  • Corroborated name matches, so common names do not block
  • Evidence file per decision for the bank partner
  • Attestation page

New chains and foundations

oracle: testnet pending
The trigger
Builders on your chain cannot get incumbents to cover it for months, and every one of them is being asked the same compliance question.
What they screen
Every app in the ecosystem, under one sponsorship, Bridge and launch flows.
What they use
  • Chain added to the registry the week it launches
  • Ecosystem-wide coverage under one agreement
  • On-chain screening oracle for contracts

Ecosystem sponsorship is available now; the on-chain oracle is built and tested, with testnet deployment pending.

AI-agent payment platforms

early
The trigger
Agents paying agents means nobody is watching the counterparty. The screen has to sit inside the payment path, not in a dashboard someone checks later.
What they screen
Payee addresses before settlement, Payer addresses on receipt, Pay-per-request endpoints.
What they use
  • Sub-50 ms address screens on the hot path
  • Exposure as best-effort, never blocking the call
  • Idempotency keys per payment
  • Webhooks for monitors

Early. The API works for this today; the integration patterns are still being written with the first platforms.

Not sure which plan? Plan guidance by segment.

Why now

Sanctions screening used to be a problem for banks and large exchanges. Five things changed, and now a wallet with a thousand users is asked the same questions.

Stablecoins are now federally regulated in the US
The GENIUS Act, signed in July 2025, made stablecoin issuers federally regulated. Issuers and their partners push compliance expectations down to the apps that use their coins.
List-only screening misses the biggest mixer
OFAC delisted Tornado Cash in March 2025. A screen that checks only the SDN list no longer flags its contracts. Clearlist keeps them as public labels, with the delisting recorded on each entry.
The SDN list is a crypto list now
OFAC's SDN list carries over 1,000 crypto addresses across more than 20 assets, from Bitcoin and Ethereum to Tron, Solana and privacy coins. Matching them needs every chain, not one.
New chains launch monthly; incumbents cover them late
Builders on a chain that launched this quarter are asked the same compliance questions as everyone else. Address screening works on a new chain immediately; exposure follows as indexers appear.
Banks and ramps de-risk what they cannot document
A bank, card program or ramp provider that cannot see a screening program in writing will often decline the client rather than ask twice. The attestation page and evidence exports exist for that conversation.

How it compares

Chainalysis, Elliptic and TRM are excellent investigation products sold to compliance teams through enterprise contracts. Name-screening APIs cover people, not wallets. Clearlist is the decision layer for a developer who has to ship screening this week. Full comparison.

 ClearlistChainalysis, Elliptic, TRMName-screening APIs
How you buySign up, create a key, call the API. No sales call.Sales-led. A call, a quote, a contract.Mostly sales-led; some offer self-serve starter plans.
Pricing visibilityPublic. Free trial, then $299 or $1,500 a month. Foundation and Enterprise from $50,000 a year.Not published. Quote-based enterprise contracts.Varies; usually quote-based above a starter tier.
Minimum commitmentNone on self-serve tiers: month to month, cancel any time. Annual billing is optional. Foundation and Enterprise are annual agreements.Annual enterprise contracts are typical.Usually an annual contract above a starter tier.
Time to first screenMinutes. The curl in the docs works with a test key.Weeks: procurement, contract, onboarding, integration.Days to weeks.
What a decision looks likeallow, review or block, with a list of reasons. Each reason has a one-sentence summary and the evidence behind it. Plus a user_message you can show your end user.A risk score or risk level with a category label. The why lives in the investigation product.Match score per name with the matched list entry. No chain context.
False-positive controlsYour policy (thresholds and actions per category), your allowlist, a review queue with one-click clear or confirm. A name never blocks on its own.Alert rules configured inside the platform; tuning is an account-management conversation.Fuzzy-match thresholds; whitelisting varies by vendor.
Evidence export and attestationA per-decision evidence file (the decision plus the complete list records and batch versions behind it), a printable attestation page with a share link, and a Compliance Pack (policy, risk assessment, procedure) generated from your real configuration.Reports and case exports from the investigation product.Match reports and audit logs.
Exposure depthOne hop today, two hops reported as information. Growing. Honest limit: this is where they are stronger.Deep multi-hop attribution graphs. This is their core strength.None.
Chain coverage45 chains screened, 32 EVM. Exposure on 32. A new chain is added the week it launches; the registry is public.Broad, Ethereum-first. New chains arrive on a roadmap, often months after launch.No chain coverage.
Investigations toolingNone. Clearlist answers the question at the point of decision; it is not a graph explorer.Excellent. Graph exploration, clustering, case management.None.

Vendor descriptions are general; their pricing is not published. Where they are stronger (attribution depth, investigations, SOC 2) the full comparison says so.

Government lists and public labels only

OFAC SDN and Consolidated, EU Financial Sanctions, UK OFSI, and the UN Security Council list, fetched from the publishers and versioned as batches. Public chain labels for mixers, hacks, scams, darknet markets and ransomware. Every entry carries its source URL. No resold third-party datasets with non-commercial terms.

Solana, Ethereum, Base, BNB Chain and Robinhood Chain first. Every EVM chain with them. Every other chain, screened.

Counterparty exposure runs on Solana, through Helius or any Solana RPC, and on all 32 EVM chains in the registry, from Ethereum, Base, BNB Chain and Robinhood Chain to Monad and HyperEVM, through one Etherscan v2 integration. Address screening against the government lists works on every chain because designated addresses are strings: Bitcoin, Tron, the UTXO chains, XRP and Monero are covered the day an address is listed. A new L1 or L2 can be added the week it launches, and a foundation can sponsor every app on it.

Start screening in the next five minutes

Sign up, copy your key, paste the curl. The dashboard shows the decision with its evidence.