Acuris Compliance Search API
★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey9 EndpointsREST
For Agents
Screen individuals and businesses against sanctions, PEP, and adverse media lists through Acuris Compliance Search.
Use for: I need to screen a customer against sanctions lists, Check whether a counterparty business is on a PEP list, Retrieve the adverse media history for an individual, Look up the sanction body issuing a flag
Not supported: Does not handle ID document verification, biometric matching, or transaction monitoring — use for sanctions, PEP, and adverse media screening of individuals and businesses only.
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.
Install Jentic One Beta
Connect the Acuris Compliance Search API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acuris Compliance Search 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.
1
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 | sh2
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 instanceJentic 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 Search API.
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
Patterns agents use Acuris Compliance Search API for, with concrete tasks.
★ 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.
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.
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.
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 the Jentic vault, and the agent searches by intent — e.g. 'screen a person for sanctions' — without compliance officers handling the raw key.
Search Jentic for 'screen an individual on Acuris', load the schema, and execute it with name, DOB, and country
Key Endpoints
9 endpoints — jentic publishes the only available openapi specification for acuris compliance search api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Acuris x-api-key values are stored encrypted in the Jentic vault. Agents receive scoped execution handles, so the raw key never appears in prompt context or logs — important for compliance audit trails.
Intent-based discovery
Agents search Jentic by intent, e.g. 'screen an individual for sanctions' or 'check a business for PEP', and Jentic returns the matching Acuris operation with its input schema.
Time to first call
Direct Acuris integration: 2-4 days for auth, response shape mapping, and evidence retrieval. Through Jentic: under 1 hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Acuris Compliance Search API through Jentic.
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 at https://app.jentic.com/sign-up.
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 the Jentic vault 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.
GET STARTED