Docs

How InsightKYC 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, a React app and PostgreSQL. InsightKYC reads the bank’s systems from a source schema and keeps its cases, checks, matches, decisions and agent runs in its own schema.

1

Connect the sources

Point KYC_SOURCE_SCHEMA at your applications, customers, registry, lists and transactions, or at views over them.

2

Set the policy

Country and industry risk, the ownership threshold and the case controls in Rules Studio.

3

Add people

Analysts, leads, 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_SCHEMAPostgreSQL connection and the schema InsightKYC keeps its own work in
KYC_SOURCE_SCHEMAThe schema holding the bank’s systems: applications, customers, the registry, documents, lists, accounts and transactions. Read only
KYC_UBO_THRESHOLDThe beneficial-ownership threshold, in percent (default 25)
KYC_AGENTS_LLM, KYC_AGENT_MODELWhether the agents use a language model, and which; off means rules only
KYC_COPILOT_LLM, KYC_CLAUDE_MODELThe same for the copilot
KYC_AGENTS_MAX_LEVELThe autonomy ceiling for every agent in the tenant
KYC_COMMS_LIVE, KYC_APP_URLWhether sending a request emails the customer, and the address the customer link points to
KYC_CORS_ORIGINSThe web origins allowed to call the API
Data

What InsightKYC reads

The demo builds these tables for a fictional bank; a deployment maps them to the bank’s systems.

Source tableWhat it holds
customers, persons, businessesThe bank’s customers and applicants
applications, related_partiesWhat the customer declared: products, purpose, expected activity, owners and officers
registry_companies, registry_officers, registry_shareholdersThe company registry the ownership agent walks
documentsIdentity, address and company documents, with the files
sanctions_entries, pep_entries, adverse_mediaThe screening lists
accounts, transactionsWhat monitoring reads
country_risk, industry_risk, bank_profileThe risk policy’s reference data
API

Every screen is an API call

Authenticated with the session’s bearer token; the customer request page is the only public route.

AreaEndpoints (under /api/kyc)
Reference and intakeGET /reference, GET /applications, POST /cases
CasesGET /cases, GET /cases/{id}, PUT /cases/{id}/owner, GET /cases/{id}/timeline, POST /cases/{id}/steps/{step}
DocumentsGET|POST /cases/{id}/documents, GET /documents/{id}, GET /documents/{id}/file
Checks and screeningGET /cases/{id}/checks, POST /checks/{id}, GET /cases/{id}/screening, POST /hits/{id}, GET /lists/search
Ownership and riskGET /cases/{id}/ownership, GET /cases/{id}/risk, POST /cases/{id}/risk/override, POST /cases/{id}/edd
RequestsGET|POST /cases/{id}/requests, PUT /requests/{id}, POST /requests/{id}/send, POST /requests/{id}/cancel; the customer’s page uses /api/public/request/{token}
DecisionPOST /cases/{id}/memo, POST /cases/{id}/submit, POST /cases/{id}/decide, GET /cases/{id}/decision
Customer book and monitoringGET /customers, POST /customers/sync, POST /customers/{id}/review, GET /alerts, POST /monitoring/run, POST /alerts/{id}/close, POST /alerts/{id}/escalate
Agents (under /api/kyc_agents)POST /cases/{id}/run, POST /portfolio/run, GET /prepared, POST /prepared/{id}/answer, GET /autonomy, GET /activity, GET /metrics

Questions about a deployment?

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

Request a demo