Paste an address or a payment, and Vernier reads the public ledger and the industry's screening providers into a single profile — organized around the four things a finance person actually needs to know. Every line names the source that reported it. None of them tells you what to conclude.
READING · TOP TO BOTTOM · SOURCE BY SOURCE
Vernier never poses the verdict — but you're allowed to. Each category answers the question you're actually asking, in sourced data, and stops exactly there.
Entity labels, ENS identity, and known-service attribution — is this an exchange, a fund, a protocol, a named business, or an unlabeled wallet?
A fund-flow trace back through the counterparty's funding sources — which exchange, which service, how many hops away.
Sanctions screening, mixer and darknet exposure, scam and drainer flags — compiled and attributed, with a composite reading beside the withheld conclusion.
Wallet age, transaction history, and balance as context — the difference between a three-year-old counterparty and one created yesterday.
Your bank rarely asks about a wallet in general. It asks about the deposit that landed on the 14th. Vernier reads both — and a memo can anchor to the specific transaction that prompted the question.
Paste a wallet and get the complete four-category profile — who they are, where their money has been, their exposure, their standing. The read you run before you take the payment.
Anchor a memo to a single transaction hash — amount, date, and USD value at the moment of transfer — with the wallet profile as supporting context. This is what a bank's question actually points at.
In 2026, "an AI wrote this document" is a fair thing to worry about — especially one you file with a bank. So the memo generator is caged: it may only phrase fields that already exist in the sourced snapshot. Every sentence traces to a datum. There is no path for free text to appear.
Template-bounded, QA-checked, and constrained at the architecture level — not asked nicely in a prompt. A single invented finding in a filed document is an existential failure, so we built it so one can't occur.
Vernier does not add, infer, or embellish. If a datum isn't in the sourced snapshot, it cannot appear in the memo.
The same business can hold many addresses, across many chains — and the same 0x address exists on Ethereum, Base, and more at once. Screenings and memos attach to the entity, and state exactly which addresses and chains they covered.
SCREENINGS ATTACH TO THE ENTITY · EACH STATES WHICH ADDRESSES AND CHAINS IT COVERED
The failure mode of monitoring is noise. Vernier's alert rules are defined up front — what always fires, and what never does — so an alert means something changed that matters.
Screening providers sometimes mislabel. Annotate any finding with context, trigger an on-demand re-screen, and the annotation is retained in the record — so the correction is part of the evidence, not a lost email.
Vernier starts where our customers' money concentrates. Each chain is a real integration, added deliberately — not a box to check. US-first.
ON THE WATCH LIST — Arbitrum and Stellar next as flow warrants, plus the emerging payment rails (Circle’s Arc, Stripe’s Tempo, and bank-issued and tokenized-deposit networks). Chains are added where the money concentrates, not to lengthen a list.
Try the full platform free for 7 days — screen, gate, book, and monitor. Then keep the record going from $79/mo.