AML and sanctions
Transaction monitoring alerts, money mule accounts and sanctions and watchlist screening. Ready-to-run Grayson recipes with real responses, cost and latency.
| Recipe | Decides | Cost per 1,000 decisions | Latency (US-West) |
|---|---|---|---|
| Detect money mule accounts | Whether an account is passing other people's money through, whether the holder knows, and what to do | $0.47 to $0.74 | 200 to 309 ms |
| Triage AML transaction monitoring alerts | Close, ask the customer, escalate or file on a transaction monitoring alert, with the typology and how likely it meets the SAR standard | $0.55 to $0.69 | 225 to 268 ms |
| Triage sanctions and watchlist screening hits | Decide whether a sanctions or watchlist hit is your customer, record why, and clear, request information, escalate or block. | $0.55 to $0.81 | 243 to 333 ms |
Each recipe has three examples with a realistic, detailed state: one with obvious fraud signals, one that is very likely legitimate, and one that is ambiguous. Cost is for those requests at $0.035 per million input tokens. Latency is the median of several calls of each through api.finic.ai from US-West; add your own network time from elsewhere.
See every category on the Recipes page.
Loan applications
Grayson screens personal loan, credit card and small-business loan applications for stolen identities, inflated income, edited pay stubs and other people's bank accounts, and picks proceed, verify income, verify identity or decline.
AML alert triage
Decide whether a transaction monitoring alert is explained by what you know about the customer, which typology it fits, how likely it meets the SAR standard, and whether to close it, ask the customer, escalate or file.