dilisense AML Screening API

Name: dilisense AML Screening API
Brand: dilisense AML Screening API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey6 EndpointsREST

For Agents

Screen individuals and entities against sanctions, PEP, and watchlists, and generate PDF compliance reports. Authenticated via the x-api-key header.

Install Jentic One Beta

Connect the dilisense AML Screening API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the dilisense AML Screening API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with dilisense AML Screening API.

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

GET STARTED

Start building with dilisense AML Screening API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use dilisense AML Screening API for, with concrete tasks.

★ 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.

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.

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?'.

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.

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

6 endpoints — jentic publishes the only available openapi specification for dilisense aml screening api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Dilisense x-api-key headers live encrypted in the Jentic vault. Agents call screening operations through Jentic without ever holding the key, which matters extra-much for compliance APIs where leaked credentials are themselves an audit finding.

Intent-based discovery

Agents search Jentic by intent — 'screen an individual against sanctions' or 'check an entity against watchlists' — and Jentic returns the matching Dilisense operation with its parameter schema.

Time to first call

Direct Dilisense integration: 1 day for x-api-key handling, response parsing, and PDF report download. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using dilisense AML Screening API through Jentic.

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 at https://app.jentic.com/sign-up.

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: <your 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.