Account security
Who is really in control of an account: takeovers, exposed credentials and employee access to customer accounts. Ready-to-run Grayson recipes with real responses, cost and latency.
| Recipe | Decides | Cost per 1,000 decisions | Latency (US-West) |
|---|---|---|---|
| Detect account takeover before money moves | Whether someone else controls an account that just changed its sign-in, contact or payout details, and whether the money should go. | $0.53 to $0.67 | 227 to 253 ms |
| Detect insider threats in employee account access | Decide whether an employee's account access is work, snooping or insider fraud, and close, refer or suspend. | $0.56 to $0.79 | 243 to 283 ms |
| Triage dark web credential and card alerts | Match a dark web alert to the customer, judge whether the exposure still works, and choose the response. | $0.53 to $0.75 | 220 to 283 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.
Fleet fuel cards
Grayson checks a fleet card's fuel authorization against the truck's telematics, its fill history and the station, separates cloned cards and fuel theft from routine fills, and picks approve, alert, decline or block.
Account takeover
Grayson decides whether someone else is controlling an account that just changed its sign-in, contact or payout details, who owns the destination, and whether to release, step up, hold or block the money.