For fintechs, exchanges, stablecoin payment firms and MSBs running AI on suspicious-activity work
Independent monthly testing of the AI agent in your SAR workflow, on your own cases, with evidence your examiner can follow.
Detection got the budget. Then agents took over triage and drafting. Now examiners ask a new question: how do you know the agent is right? Your vendor can’t answer that for you.
On March 2, Harlow Trading received a wire of $48,500 A1 and within four hours sent $45,800 in USDC to an external wallet T4. Funds reached a high-risk exchange in two hops C2. missing · why it’s suspicious
Tested once, on someone else’s data. Agents change with every release.
12 times a year, on your cases.
We map your agent, deploy the engine read-only in your cloud, review 60–120 cases and deliver a baseline report and remediation plan.
Your agent’s error rate, measured on your own cases.
Monthly QA runs, a quarterly re-tune and re-test, and a live model and prompt register.
Evidence that keeps pace with every release.
The full evidence binder and a board summary. Triggered early by a model change, a new typology or an exam letter.
One binder an examiner can follow end to end.
Baseline delivered within 4 weeks of data access, or we keep working free and your first month is on us.

I test the AI that handles what happens after the alert fires.
My background is statistics and applied analytics: seven years measuring model performance, false positive rates and where automated systems fail. That discipline is what AML programs need and rarely have. Monitoring stacks get tuned on intuition, and few teams can show an examiner why a threshold sits where it does.
I work across BSA/AML, OFAC, the FATF Travel Rule and the GENIUS Act stablecoin rules, and I read chains directly rather than relying on a vendor’s attribution. Most compliance stacks see the fiat leg and go blind at the chain boundary.
Novaheim is independent. We don’t resell AML platforms, and we never test a workflow we built.
Their validation covers their platform. Your examiner looks at how you use it: your prompts, typologies, thresholds and data. We test that, every month.
No. Our access is read-only. We never draft, edit or file a SAR, and we never close an alert.
Everything runs in your cloud, on your model endpoint. Nothing is copied to Novaheim or used for training. Access is time-boxed, approved per session and limited to named roles.
Novaheim’s test engine, deployed read-only under your access controls. It’s the same engine every client runs, maintained and updated by us, so you get every new check without building or running it yourselves. Your data and results never leave your deployment. The engine runs for as long as your engagement does.
Every number comes from versioned SQL against your records. The AI only judges language quality and quotes its evidence, and a person reviews every flag. The judge’s own accuracy is measured and recorded in the register.
Any agent whose drafts and dispositions you can export or reach through an API, whether from a vendor or built in-house.
A few hours to grant access and kick off the baseline, then about 2–4 hours a month for your BSA Officer to review and sign.
No one can promise an exam outcome. We produce the evidence examiners ask for: what you tested, what you found and what you fixed. You own it.
No. It feeds into it, and we work with your auditor.
You do. Every report, finding and sign-off, and the write-once log, stay in your environment and stay yours. If the engagement ends, we remove the engine; the evidence stays where it is.
Ready to start?
Agents change every release. Examiners ask every cycle. Start with a 30-day baseline.