Reference build: a compliance monitoring SaaS
A B2B compliance product screens addresses, monitors activity and gives analysts the context to work a case. This build combines the risk, monitoring and graph primitives into one backend so your customers get screening, alerts and investigation from a single key.
The challenge
Building a compliance SaaS usually means licensing a scoring engine, a monitoring feed and a graph tool, then reselling them under your brand. The goal is to source scoring, KYT, counterparty graph and fund-flow tracing from one key so your product owns the workflow, not a stack of vendor dashboards.
- Address risk-score / exposureC3
- Transaction screening / KYTC3
- Counterparty graphC3
- Fund-flow trace (hops)C4
Score at onboarding
Call risk-score on each address your customers add and store score, confidence and exposure, so onboarding produces a reproducible decision inside your product.
Monitor with KYT
Route ongoing transactions through KYT to keep producing allow/review/block decisions, feeding a case queue in your UI rather than a static export.
Investigate with graph and tracing
When an alert escalates, surface the counterparty graph and trace funds across hops to document exposure to mixers or sanctioned clusters before an analyst signs off.
What the build delivers
- Onboarding scoring and ongoing KYT under your own brand
- Counterparty graph and fund-flow trace built into the case workflow
- One key behind the product instead of three reselling vendor dashboards
Frequently asked
Can I resell this under my brand?
Yes — the primitives sit behind your product, so your customers see your workflow and UI, not a licensed vendor dashboard.
What supports case investigation?
The counterparty graph and fund-flow trace document exposure across hops, giving analysts the context to escalate or clear a case.
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key