Acuris Compliance API

Name: Acuris Compliance API
Brand: Acuris Compliance API
Availability: InStock

✓ Official Vendor SpecIdentity AuthIdentity VerificationapiKey9 EndpointsREST

For Agents

Screen individuals and businesses against Acuris sanctions, PEP, and adverse-media data, retrieve full compliance profiles, and pull PDF evidence reports.

Install Jentic One Beta

Connect the Acuris Compliance API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acuris Compliance 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 Acuris Compliance API.

Search the individuals database for a person by name and attributes via /individuals

Search the businesses database for a corporate entity through /businesses

Retrieve a full individual compliance profile by resourceId via /individuals/{resourceId}

GET STARTED

Start building with Acuris Compliance API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Acuris Compliance API for, with concrete tasks.

★ Customer onboarding screening

Run KYC and KYB screening at account opening by calling /individuals or /businesses with the applicant's name, then resolving to the full profile via /individuals/{resourceId}. Acuris returns sanctions hits, PEP classification, adverse media articles, and law enforcement notices, each tagged with the source body and date. Lets a fintech or bank decide accept, refer, or reject within a single onboarding call.

Call /individuals?name=John+Smith&dob=1980-01-01, take the top resourceId, then /individuals/{resourceId} and return the sanctions and PEP sections.

Ongoing transaction monitoring

Re-screen existing customers and counterparties on a schedule by storing each resourceId and refetching /individuals/{resourceId} or /businesses/{resourceId} periodically. Changes in PEP status, new sanctions, or adverse media surface in the response and can be turned into review tickets. Pairs naturally with a transaction-monitoring engine that flags spikes in counterparty risk.

For each stored resourceId, call /businesses/{resourceId} weekly and diff the sanctions array; raise a case if a new sanction body appears.

Audit-ready evidence pull

When a regulator or internal audit asks for proof of why a customer was accepted or rejected, fetch the corresponding PDF evidence using /individuals/{resourceId}/evidences/copyrighted/{evidenceId}. Acuris evidence files preserve the original source article or sanctions notice, satisfying the documentation requirements of EU 6AMLD, FCA, and FinCEN. Removes the need to manually screenshot upstream sources.

Given resourceId and evidenceId from a stored case, call /individuals/{resourceId}/evidences/copyrighted/{evidenceId} and persist the PDF to the case file.

Agent integration via Jentic

Equip a compliance agent with three primitives - search, fetch profile, fetch evidence - without writing client code. Through Jentic the agent receives the operation schemas for /individuals, /individuals/{resourceId}, and the evidence endpoint, and the Acuris x-api-key lives in your Jentic One instance. The agent can answer 'is this customer flagged?' in a single tool call.

Search Jentic for 'screen a customer for sanctions', load /individuals, and execute it with name=Acme+Holdings to return any matching profiles.

Key Endpoints

9 endpoints — the acuris compliance api exposes the acuris (formerly c6) database of individuals and businesses with sanctions, politically exposed person, adverse media, and law-enforcement profile data used by financial institutions for kyc, kyb, and ongoing monitoring.

METHOD

PATH

DESCRIPTION

GET

/individuals

Search compliance profiles for natural persons

GET

/individuals/{resourceId}

Retrieve a full individual compliance profile

GET

/businesses

Search compliance profiles for corporate entities

GET

/businesses/{resourceId}

Retrieve a full business compliance profile

GET

/individuals/{resourceId}/evidences/copyrighted/{evidenceId}

Download copyrighted evidence PDF for an individual

GET

/dictionaries/sanction-bodies

List recognised sanction-issuing bodies

GET

/individuals

Search compliance profiles for natural persons

GET

/individuals/{resourceId}

Retrieve a full individual compliance profile

GET

/businesses

Search compliance profiles for corporate entities

GET

/businesses/{resourceId}

Retrieve a full business compliance profile

GET

/individuals/{resourceId}/evidences/copyrighted/{evidenceId}

Download copyrighted evidence PDF for an individual

Why Jentic?

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

Credential isolation

Your Acuris x-api-key is stored once, encrypted, by your own Jentic One instance and injected as the header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'screen a customer for sanctions', and Jentic returns the matching Acuris operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Acuris Compliance API through Jentic.

What authentication does the Acuris Compliance API use?

The Acuris Compliance API uses an API key in the x-api-key header on every request. Keys are issued by Acuris under a paid contract and scoped per environment. Through Jentic the key is stored in your Jentic One instance and injected at execution time so it never appears in agent prompts.

Can I screen both people and companies with the Acuris Compliance API?

Yes. Use /individuals and /individuals/{resourceId} for natural persons (covering sanctions, PEP, and adverse media) and /businesses and /businesses/{resourceId} for corporate entities. Both endpoints expose the same shape of compliance profile, so a single agent can handle KYC and KYB.

How do I retrieve the underlying evidence for a sanctions or adverse media hit?

Each profile contains evidence references with a copyrighted evidenceId. Call /individuals/{resourceId}/evidences/copyrighted/{evidenceId} (or the equivalent /businesses path) to download the source PDF. These files preserve the upstream sanctions notice or news article and are suitable for regulator-facing audit packs.

What are the rate limits for the Acuris Compliance API?

Rate limits are set per contract by Acuris and surfaced in your account portal - typical enterprise tiers permit several requests per second per key. Agents should back off on 429 responses and cache profile reads where appropriate to stay within the contracted ceiling.

How do I run an Acuris sanctions check through Jentic?

Search Jentic for 'screen a customer for sanctions', load the /individuals search operation, and execute it with name and (optionally) dob and country. Take the top resourceId, then call /individuals/{resourceId} to fetch the full profile including sanctions, PEP, and adverse media sections.

Is the Acuris Compliance API free?

No. Acuris is a commercial dataset and access is paid, typically priced per screening volume under an enterprise contract. Contact Acuris directly to provision a key for production use; sandbox keys may be available through pilot programmes.

Can I limit what my agent is allowed to do with the Acuris Compliance API?

Yes. Because you self-host Jentic One, your own rules decide which Acuris operations and credentials the agent may use. Since Acuris carries the resource id in the URL path (/individuals/{resourceId}, /businesses/{resourceId}), you can pin the agent to a single individual or business so it fetches only that profile and its copyrighted evidence and nothing else. You choose the operations it can call, so broad screening searches against /individuals or /businesses are available only if you add them, and the Acuris x-api-key stays with your instance rather than in the agent's prompt.