canonical: https://jentic.com/apis/acuris.com/acuris

# Acuris Compliance Search API

Jentic publishes the only available OpenAPI specification for Acuris Compliance Search API, keeping it validated and agent-ready. Acuris Compliance Search lets compliance teams screen individuals and businesses against sanctions, politically exposed persons (PEP), and adverse media data. The spec covers nine endpoints split across individuals, businesses, and reference dictionaries, with copyrighted evidence retrieval available per resource. Authentication is via the x-api-key header, scoped to the compliance subscription tier.

## For AI agents

Screen individuals and businesses against sanctions, PEP, and adverse media lists through Acuris Compliance Search.

## Scope

Does not handle ID document verification, biometric matching, or transaction monitoring - use for sanctions, PEP, and adverse media screening of individuals and businesses only.

## Capabilities

- Search individual compliance profiles via /individuals
- Retrieve a full individual profile by id at /individuals/{resourceId}
- Search business compliance profiles via /businesses
- Retrieve a full business profile by id at /businesses/{resourceId}
- Pull copyrighted evidence attached to an individual or business profile via the /evidences/copyrighted/{evidenceId} sub-resource
- Look up reference data such as sanction body codes through /dictionaries/sanction-bodies

## Use cases

### KYC sanctions screening

Banks and fintech onboarding flows screen new customers against sanctions and PEP lists before approving accounts. An agent can call /individuals with name and date of birth, review hits, then GET /individuals/{resourceId} for the full profile and supporting evidence. This becomes the structured KYC step in an automated onboarding pipeline.

Example prompt: Search /individuals for 'John Doe, DOB 1985-04-12, country GB', then fetch the top hit's full profile via /individuals/{resourceId}

### Counterparty business due diligence

Procurement and finance teams screen suppliers and counterparties before signing contracts. An agent can search /businesses for the legal entity name and jurisdiction, then pull /businesses/{resourceId} for sanctions, ownership, and adverse media findings. Pair this with a contract management tool to attach the evidence to the supplier record.

Example prompt: Search /businesses for 'Acme Holdings Ltd' in 'GB', then GET /businesses/{resourceId} and attach copyrighted evidence ids to the supplier record

### Audit trail with copyrighted evidence

Auditors need the source documents that justify a sanctions or adverse media match. The /evidences/copyrighted/{evidenceId} sub-resources on both /individuals and /businesses return the underlying evidence record. An agent can store the evidence id and a hash so future audits can re-fetch the same source on demand.

Example prompt: Fetch evidence id 'ev-789' from /individuals/{resourceId}/evidences/copyrighted/ev-789 and store it in the audit log

### AI agent integration

Compliance teams building agent assistants expose Acuris through Jentic to wrap KYC into a conversational tool. The x-api-key value lives in your Jentic One instance, and the agent searches by intent - e.g. 'screen a person for sanctions' - without compliance officers handling the raw key.

Example prompt: Search Jentic for 'screen an individual on Acuris', load the schema, and execute it with name, DOB, and country

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /individuals | Search individual compliance profiles |
| GET | /individuals/{resourceId} | Retrieve a full individual profile |
| GET | /businesses | Search business compliance profiles |
| GET | /businesses/{resourceId} | Retrieve a full business profile |
| GET | /individuals/{resourceId}/evidences/copyrighted/{evidenceId} | Retrieve copyrighted evidence for an individual |
| GET | /businesses/{resourceId}/evidences/copyrighted/{evidenceId} | Retrieve copyrighted evidence for a business |
| GET | /dictionaries/sanction-bodies | List sanction body codes |

## Key resources

- **Individuals** — Search and retrieve individual compliance profiles
- **Businesses** — Search and retrieve business compliance profiles
- **Evidences (copyrighted)** — Source documents supporting a compliance match
- **Dictionaries** — Reference data such as sanction bodies

## Why Jentic

- **Setup:** Wiring the Acuris Compliance Search API by hand means attaching the x-api-key header on every call and threading resource and evidence ids through the individuals and businesses screening endpoints. Through Jentic you install once, import the Acuris Compliance Search API from the API Directory, store the x-api-key once, and your agent calls it.
- **Permission scoping:** Acuris puts the resource id in the URL path (/individuals/{resourceId}, /businesses/{resourceId}), so a rule can pin your agent to reading a specific screening record and its evidence and nothing else. You choose the operations it may call, so business screening is not included unless you add it.
- **Credential handling:** Your Acuris x-api-key is stored once, encrypted, by your own Jentic One instance and injected as the x-api-key header 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 for sanctions' or 'check a business for PEP', and Jentic returns the matching Acuris operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **ComplyAdvantage API** — Real-time AML and sanctions screening with continuous monitoring.
- **Onfido API** — Identity verification with document and biometric checks alongside sanctions screening.
- **Action Network API** — Different domain, but useful in agent stacks that combine compliance with civic engagement data.

## FAQ

### Why is there no official OpenAPI spec for Acuris Compliance Search API?

Acuris does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Acuris Compliance Search 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 Acuris Compliance Search API use?

Acuris uses an API key passed in the x-api-key header. The key is issued by Acuris on subscription. Through Jentic, the x-api-key is stored encrypted in your Jentic One instance and the agent receives a scoped execution handle, so the raw key never enters the agent's context or logs.

### Can I screen individuals and businesses with the Acuris Compliance Search API?

Yes. GET /individuals returns matches for an individual query, and GET /individuals/{resourceId} returns the full profile including sanctions, PEP, and adverse media findings. The same pattern applies to /businesses for legal entities. Copyrighted source evidence is available under /evidences/copyrighted/{evidenceId} on each profile.

### What are the rate limits for the Acuris Compliance Search API?

The OpenAPI spec does not declare rate limits - they are tied to the subscription tier. Check the Acuris developer portal for your tier's ceiling, and batch screening should be paced accordingly with exponential backoff on 429 responses.

### How do I run a sanctions check through Jentic?

Run pip install jentic, search Jentic for 'screen a person on Acuris', load the schema for GET /individuals, and execute it with name, date of birth, and country. Jentic injects the x-api-key from the vault, so the agent only supplies the search criteria.

### Does Acuris return source evidence for compliance matches?

Yes. Each individual and business profile exposes an /evidences/copyrighted/{evidenceId} sub-resource that returns the underlying source document for an audit trail. Storing the evidence id alongside the screening decision lets auditors re-fetch the same source later.

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

Yes. Because you run Jentic One yourself, your own rules decide which Acuris operations the agent may call, so you can allow individual screening through GET /individuals and GET /individuals/{resourceId} while withholding business screening on /businesses until you choose to add it. Acuris puts the resource id in the URL path, so a rule can pin the agent to reading one specific screening record and its copyrighted evidence under /evidences/copyrighted/{evidenceId} and nothing else. Your Acuris x-api-key stays with your own instance and is attached at execution time, so the agent never sees the raw key.