OpenSanctions API

Name: OpenSanctions API
Brand: OpenSanctions API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey8 EndpointsREST

For Agents

Search and match persons and companies against sanctions, PEP, and related risk lists via the OpenSanctions API.

Install Jentic One Beta

Connect the OpenSanctions API to your agent

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

Run free-text search against a chosen OpenSanctions dataset

Submit a structured entity (name, country, birthDate) for fuzzy matching against a dataset

Retrieve a full entity record by ID, including aliases and source statements

GET STARTED

Start building with OpenSanctions API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use OpenSanctions API for, with concrete tasks.

★ KYC sanctions screening

A regulated business screens new customers against OpenSanctions during onboarding by submitting a structured record (name, date of birth, country) to the match endpoint. The API returns scored candidate entities so the compliance team can adjudicate high-confidence hits without scraping individual sanction lists.

POST to /match/{dataset} with the customer's name, country, and birthDate against dataset='default' and inspect candidates with score above 0.7.

Investigative entity exploration

Investigative journalists and analysts pull a starting entity by ID, then walk the adjacency graph via /entities/{entityId}/adjacent to discover related companies, beneficiaries, and PEP relationships. The statements endpoint exposes the underlying source records, supporting rigorous citation in published work.

GET /entities/{entityId} for the target, then GET /entities/{entityId}/adjacent and follow the highest-confidence directorship edges.

Vendor risk batch screening

A procurement team runs its full vendor list through OpenSanctions on a recurring schedule by querying /search/{dataset} for each vendor name and flagging any non-empty hits. Recurring screening covers the case where a previously clean vendor later appears on a new list.

Iterate the vendor list, GET /search/{dataset}?q=vendor_name, and write any non-empty result into the risk register for human review.

Agent-driven sanctions screening through Jentic

An onboarding agent calls OpenSanctions via Jentic to screen new accounts before activation, using the match endpoint for structured fields and falling back to text search for ambiguous inputs. Jentic isolates the API key so the agent can run thousands of screenings without ever holding the secret directly.

Search Jentic for 'match a person against sanctions', load /match/{dataset}, and execute it for the new customer record at dataset='default'.

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for opensanctions api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/search/{dataset}

Run text search against a dataset

POST

/match/{dataset}

Run structured entity match against a dataset

GET

/entities/{entityId}

Retrieve an entity record by ID

GET

/entities/{entityId}/adjacent

List entities adjacent to a given entity

GET

/statements

Query underlying statements

GET

/catalog

Browse datasets in the catalog

GET

/algorithms

List supported matching algorithms

GET

/search/{dataset}

Run text search against a dataset

POST

/match/{dataset}

Run structured entity match against a dataset

GET

/entities/{entityId}

Retrieve an entity record by ID

GET

/entities/{entityId}/adjacent

List entities adjacent to a given entity

GET

/statements

Query underlying statements

Why Jentic?

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

Credential isolation

Your OpenSanctions API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'match a person against sanctions' or 'search OpenSanctions for a company', and Jentic returns the matching match or search operation with its dataset path parameter and request schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using OpenSanctions API through Jentic.

Why is there no official OpenAPI spec for OpenSanctions API?

OpenSanctions did not previously publish an OpenAPI specification in this exact shape. Jentic generates and maintains this spec so that AI agents and developers can call OpenSanctions 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 OpenSanctions API use?

OpenSanctions uses an API key passed in the Authorization header. Through Jentic the key is held in the encrypted vault and injected at request time so the agent never sees the raw value, even when running batch screenings.

Can I match structured customer records, not just names?

Yes. POST /match/{dataset} accepts a structured query with fields like name, country, and birthDate, and returns scored candidate entities. This is more accurate than free-text /search for KYC use, where extra signals reduce false positives.

What are the rate limits for the OpenSanctions API?

OpenSanctions applies tier-based rate limits and dataset entitlements that are not encoded in the OpenAPI spec; the API key carries the entitlement. Check your account dashboard before scheduling high-volume batch screenings.

How do I screen a customer through Jentic?

Run pip install jentic, search 'match a person against sanctions', load /match/{dataset}, and execute it with the structured customer fields. Jentic injects the Authorization header and returns the candidate list with match scores.

Which datasets are available?

Browse /catalog to see datasets such as the default consolidated list, regional sanctions, and PEP collections. Pass the chosen dataset slug in the {dataset} path parameter on the search and match endpoints.

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

Yes. Jentic One is self-hosted, so your own rules decide which OpenSanctions operations and credentials the agent may use. Because the entity id sits in the URL path at GET /entities/{entityId}, you can pin the agent to a single entity so it only reads that record and its adjacent entities and nothing else. Broader operations like POST /match/{dataset} or GET /search/{dataset} stay off unless you explicitly add them.