Compose an AML policy. Export a machine-readable AP2 mandate.
Translate BSA program controls, transaction-monitoring rules, and customer-risk policy
into a structured AP2 v1.0 JSON mandate an agentic payment system can read, follow, and audit
against. Configure customer risk tiers, TM rule parameters, SAR-filing triggers, sanctions screening
cadence and escalation workflows; the mandate emits as
@ainumbers.co/aml-mandate-v1.
U.S. Bank Secrecy Act (31 USC §5311 ff.) remains the foundational AML regime; FinCEN's AML/CFT National Priorities set the 2026 examination focus. FATF Recommendation 16 (the Travel Rule) and the 6th AML Directive (EU 2018/1673) add personal liability for senior management. AMLA (EU) begins direct supervision of selected obliged entities from 2028 with a single rulebook (Regulation (EU) 2024/1624).
Pick the policy domain
Each use case maps to a slice of an AML programme. Combine multiple to compose a multi-domain mandate.
Tier thresholds
Composite risk score (0–100) blends geographic, product, customer-type and behavioural factors. Tier boundaries determine onboarding friction, monitoring frequency and EDD obligations.
Transaction-monitoring thresholds
Calibrate three families of TM rules. Lower thresholds raise sensitivity (and false positives); higher raises miss-rate (and SAR exposure). The mandate emits explicit threshold floors for the runtime to enforce.
Cadence & workflow
Lower-cadence sanctions screening reduces friction but extends exposure window. SAR filing deadline is FinCEN's hard 30 calendar days from initial detection.
AP2 output
Live preview. Switch tabs to see what an agent will load, what your CCO will sign, and what an MCP client will discover.
Compose with
Pair with #11 — AML Transaction Monitoring Rule Builder to expand the TM rule layer, or #7 — AP2 Visual Policy Guardrail to visualise the same mandate as agent-traversal guardrails. The full 259-tool atlas is at the Tool Chain Composer — #23 sits inside the Agentic Runtime cluster.