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.

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.