Docs

How InsightAML is put together

Configuration, the data it reads and the API behind every screen.

Getting started

How a deployment fits together

A Python (FastAPI) API on port 8152 in development, a React and TypeScript app, and PostgreSQL. InsightAML reads the bank’s systems from a source schema and keeps its alerts, cases, SARs, requests, decisions and agent runs in its own.

1

Connect the sources

Point AML_SOURCE_SCHEMA at your transactions, customers, counterparties, invoices and lists, or at views over them.

2

Set the policy

Rule parameters, the filing clock, the jurisdiction list and the disposition and filing controls in Rules Studio.

3

Add people

Analysts, leads (curator), administrators and auditors, through the identity service or your SSO.

Configuration

The settings that matter

Set in the environment of the API.

VariableWhat it sets
INSIGHT_DATABASE_URL, INSIGHT_DATABASE_SECRET, INSIGHT_DATABASE_SCHEMAThe platform PostgreSQL connection (or a secret holding it) and the schema InsightAML keeps its own work in (aml by default)
AML_SOURCE_SCHEMAThe schema holding the bank’s systems (aml_data by default). Read only: InsightAML never writes there
AML_REVIEW_DAYSThe monitoring review window in days (default 90)
AML_FILING_DAYSThe filing clock in days from the determination (default 30). Configurable policy: set it from the filing rule that applies to you
AML_AGENTS_LLM, AML_AGENT_MODEL, AML_CLAUDE_MODELWhether the agents use a language model, and which; 0 means rules only
AML_COPILOT_LLMThe same switch for the copilot; off, it answers with the case’s headline facts
AWS_REGIONWhere the model is called (Amazon Bedrock in the reference set-up)
AML_AGENTS_MAX_LEVELThe autonomy ceiling for every agent in the tenant; every action is also capped at L2 in the code
AML_APP_URLThe address a request link points to (/request/<token>)
AML_COMMS_LIVEOpts in to live delivery outside production; otherwise a released request is a dry run
AML_CORS_ORIGINSThe web origins allowed to call the API, comma-separated; * is never honoured
Data

What InsightAML reads

The demo builds these for a fictional bank (about 1,060 customers and 190,000 transactions over twelve months, all generated); a deployment maps them to the bank’s systems.

Source dataWhat it holds
Customers and accountsEach customer’s declared profile from onboarding (expected monthly credits and debits, cash share, countries, purpose), KYC risk rating, relationship manager, and accounts
TransactionsBooked date, account, amount, direction, channel (cash, wire, ACH, person-to-person, internal), counterparty, country and branch
Counterparties and branchesWho the bank’s customers deal with, including the bank’s own customers on the other side
Trade invoices and commodity pricesInvoices with goods, quantity and unit price, and a reference price band per commodity code
JurisdictionsThe bank’s high-risk and prohibited list
Watchlist and counterparty linksWatchlist entries and registry links between counterparties and entries, with their source
Prior SARs and alert historyReports filed before, and the legacy monitoring system’s alerts and how each closed
API

Every screen is an API call

Authenticated with the session’s bearer token; the request-for-information page and the health checks are the only public routes.

AreaEndpoints (under /api/aml unless shown)
Reference and monitoringGET /reference, GET /alerts, GET /alerts/{id}, POST /monitoring/run
CasesGET /cases, GET /cases/{id}, PUT /cases/{id}/owner, POST /cases/{id}/start, GET /cases/{id}/timeline, GET /cases/{id}/decisions
InvestigationGET /cases/{id}/network, GET /cases/{id}/activity, GET /cases/{id}/profile, GET /cases/{id}/history
DispositionPOST /cases/{id}/determine, POST /cases/{id}/referral/decline
SARsGET /sars, PUT /sars/{id}, POST /sars/{id}/draft, POST /sars/{id}/submit, POST /sars/{id}/decide
Requests for informationGET|POST /cases/{id}/requests, PUT /requests/{id}, POST /requests/{id}/send, POST /requests/{id}/cancel; the recipient’s page uses GET|POST /api/public/request/{token} (no sign-in)
CustomersGET /customers, GET /customers/{cid}, GET /customers/{cid}/network, GET /customers/{cid}/activity
TuningGET /tuning, PUT /scenarios/{code} (a lead, with a reason)
Agents (under /api/aml_agents)POST /cases/{id}/run, GET /cases/{id}, POST /portfolio/run, GET /portfolio, GET /prepared, POST /prepared/{id}/answer, GET /autonomy, PUT /autonomy/{agent}/level, GET /activity, GET /metrics
Rules Studio, copilot, health/api/aml_rules (the shared Studio API), /api/assist and /api/chat (copilot), GET /api/me, GET /api/health, GET /api/ready

Questions about a deployment?

Tell us about your monitoring and case systems and we’ll map them to InsightAML’s sources with you.

Request a demo