canonical: https://jentic.com/apis/api.dilisense.com/dilisense # dilisense AML Screening API Jentic publishes the only available OpenAPI specification for dilisense AML Screening API, keeping it validated and agent-ready. Dilisense screens individuals and entities against global sanctions, PEP, and watchlist sources to support compliance with national and international AML regulations. Three core checks (individual, entity, and generic name) plus matching PDF report generators and a sources catalogue let compliance teams run on-demand screenings inside onboarding flows, payment release decisions, and periodic customer review. Authentication uses an x-api-key header issued by Dilisense. ## For AI agents Screen individuals and entities against sanctions, PEP, and watchlists, and generate PDF compliance reports. Authenticated via the x-api-key header. ## Scope Does not handle ID document verification, biometric checks, or transaction monitoring - use for sanctions, PEP, and watchlist screening of individuals and entities only. ## Capabilities - Screen an individual against sanctions and PEP lists via /checkIndividual - Screen a corporate entity against sanctions lists via /checkEntity - Screen a free-text name across all entity types via /checkName - Generate a PDF compliance report for an individual via /generateIndividualReport - Generate a PDF compliance report for an entity via /generateEntityReport - Enumerate the screening sources currently covered via /getSourceList ## Use cases ### Customer Onboarding AML Screening Add an automated sanctions and PEP check to your customer onboarding flow. Call /checkIndividual with the customer's name, date of birth, and country to receive a structured match list with hit confidence and source. False-positive rates drop sharply with a date of birth on the request, which is the difference between a 30-second compliance step and a multi-hour manual review. Example prompt: Call GET /checkIndividual with names='Jane Doe', dob='1985-03-12', country='GB' and flag the customer for review if any hit returns confidence above 70 ### Payment Release Counterparty Check Before releasing a high-value payment, screen the receiving entity against sanctions lists with /checkEntity. Pair with /checkName when you only have a free-text label. The response carries match details, source list, and hit confidence so the payment-ops engine can hold, escalate, or release accordingly without a human round trip on every transaction. Example prompt: Call GET /checkEntity with name='Acme Holdings Limited' before releasing a £250k payment and hold if any sanctions hit is returned ### Audit-Ready Compliance Reporting Compliance teams keep a paper trail by generating PDF screening reports and storing them in the audit log. /generateIndividualReport and /generateEntityReport return a downloadable PDF tied to the same query as the live check, so auditors can match each onboarding decision to a report on the same source data. /getSourceList enumerates the sources covered when an auditor asks 'what does Dilisense actually screen against?'. Example prompt: Call /generateIndividualReport for a flagged customer to produce a PDF and attach it to the case file in the compliance system ### AI Agent Compliance Co-Pilot An AI agent uses Dilisense via Jentic to handle in-conversation AML checks during analyst triage. The agent searches Jentic by intent, loads the right screening schema, and executes the call without ever holding the x-api-key. Because results are structured, the agent can summarise hits in plain language for the analyst rather than dumping raw JSON. Example prompt: Search Jentic for 'screen an individual against sanctions', load the schema, and run the check for a customer the analyst names in chat ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/checkIndividual` | Screen an individual against sanctions and PEP lists | | GET | `/checkEntity` | Screen a corporate entity against sanctions lists | | GET | `/checkName` | Screen a free-text name across all entity types | | GET | `/generateIndividualReport` | Generate a PDF report for an individual screening | | GET | `/generateEntityReport` | Generate a PDF report for an entity screening | | GET | `/getSourceList` | List the screening sources covered | ## Key resources - **Screening** — Individual, entity, and name checks against sanctions, PEP, and watchlists - **Reports** — PDF compliance reports for individuals and entities - **Sources** — Catalogue of the screening sources currently covered ## Why Jentic - **Setup:** Wiring dilisense by hand means setting up its x-api-key header auth and building your own screening plumbing against its checkIndividual, checkEntity, and report endpoints. Through Jentic you install once, import the dilisense AML Screening API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** dilisense screening targets travel as query parameters, not resource ids in the URL path, so scope the agent to the operations it needs: you can allow read-only screening such as checkIndividual and checkEntity while leaving report generation like generateIndividualReport out of the allowed set. Every operation you grant is your explicit choice. - **Credential handling:** Your dilisense API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'screen an individual against sanctions' or 'check an entity against watchlists', and Jentic returns the matching dilisense operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ComplyAdvantage API** — ComplyAdvantage provides similar sanctions, PEP, and adverse-media screening with broader media-coverage sources. - **Onfido API** — Onfido handles document verification and biometric checks that pair with Dilisense's list-based screening. - **Sumsub API** — Sumsub bundles document verification, KYC, and sanctions screening into one platform. ## FAQ ### Why is there no official OpenAPI spec for dilisense AML Screening API? Dilisense documents the API on developers.dilisense.com but does not publish a downloadable OpenAPI specification suitable for code generation. Jentic generates and maintains this spec so that AI agents and developers can call dilisense AML Screening API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the dilisense API use? Dilisense uses an `x-api-key` header issued from the Dilisense dashboard. Every screening call must include `x-api-key: `. Jentic stores the key encrypted in the vault so agents never see it; the header is injected at execution time. ### Can I screen an individual against sanctions and PEP lists? Yes - GET /checkIndividual takes name plus optional dob, gender, and country parameters and returns a list of structured hits with source, hit type (sanctions, PEP, criminal), and confidence score. Always pass dob when you have it; date-of-birth filtering dramatically reduces false-positive rates compared with name-only screening. ### What are the rate limits for the dilisense API? Dilisense applies plan-based rate limits - typical paid tiers offer thousands of screenings per day with bursts of several requests per second. The exact limit is set on your account; check the Dilisense dashboard. If a 429 response is returned, back off and retry with exponential delay. ### How do I add an AML check to an onboarding flow through Jentic? Run `pip install jentic`, search for 'screen an individual against sanctions', load the GET /checkIndividual schema, and execute with name, dob, and country at signup time. Jentic returns the structured hit list which the onboarding service can use to auto-approve, hold for review, or reject - with the screening run logged for compliance. ### Can I generate a PDF report for an audit? Yes - /generateIndividualReport and /generateEntityReport produce downloadable PDF reports with the same screening data. Store the PDF alongside the case file so auditors can trace each decision back to a contemporaneous report. Use /getSourceList to document which sources were in scope at the time of screening. ### Can I limit what my agent is allowed to do with the Dilisense AML Screening API? Yes. Because you self-host Jentic One, your own rules decide which Dilisense operations and credentials the agent may use, and screening targets travel as query parameters rather than resource ids in the URL path, so you scope the agent to only the operations it needs. For example, you can allow read-only screening such as checkIndividual and checkEntity while leaving PDF report generation like generateIndividualReport and generateEntityReport out of the allowed set. Every operation the agent can call is your explicit choice, and the API key is injected at execution time so the agent never handles it directly.