Acuris Compliance API

Name: Acuris Compliance API 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.

Quickstart

Get started with Acuris Compliance API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"screen a customer for sanctions and PEP risk"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Acuris Compliance API 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}

Retrieve a full business compliance profile by resourceId via /businesses/{resourceId}

GET STARTED

Start building with Acuris Compliance API API

Explore with Jentic

View OpenAPI Spec

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. Agents can search for a name and resolve to a canonical profile, retrieve the full profile JSON, and download a PDF compliance report including the underlying source evidence. Profile evidence is copyrighted and exposed via dedicated evidence endpoints. Built for compliance teams that need authoritative screening data behind their onboarding and transaction-monitoring flows.

Use Cases

Patterns agents use Acuris Compliance API 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 the Jentic vault. 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 though Jentic?

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

Credential isolation

Acuris x-api-key credentials are stored encrypted in the Jentic vault. Agents receive scoped execution rights, the raw key never leaves Jentic, and key rotation does not require touching agent code.

Intent-based discovery

Agents search by intent (e.g. 'screen a customer for sanctions') and Jentic returns the right Acuris operation — search, profile fetch, or evidence download — with the required parameters, so the agent picks the correct entry point without reading the full Acuris docs.

Time to first call

Direct Acuris integration: 1-2 weeks for auth, profile parsing, evidence handling, and audit logging. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ComplyAdvantage API

Comparable AML screening across sanctions, PEP, and adverse media

Choose ComplyAdvantage when the team prefers its data feed or already has a contract; choose Acuris when audit pulls the C6/Acuris source corpus.

Alternative

OpenSanctions API

Open-data sanctions and PEP dataset suitable for non-enterprise use cases

Choose OpenSanctions for low-volume or research use; choose Acuris when regulatory-grade adverse media and evidence preservation are required.

Complementary

Onfido API

Document and biometric identity verification to pair with Acuris screening

Use Onfido to verify the applicant is who they claim to be, then use Acuris to screen the verified identity against sanctions and PEP lists.

FAQs

Specific to using Acuris Compliance API 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 the Jentic vault 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.