Screen a person's name for PEP status

The /screen/pep endpoint checks a person's name against the OpenSanctions politically exposed persons (PEP) dataset. A PEP is someone who holds or has held a prominent public position — heads of state, senior government officials, senior executives of state-owned enterprises, and their close associates. Screening for PEP status is a separate concern from sanctions screening: a person can be a PEP without appearing on any sanctions list, and the response shape is distinct from the standard screening envelope.

How to use it

Send a GET request to /api/v1/screen/pep/{name}, replacing {name} with the person's full name.
Optionally include a birth_date query parameter (to disambiguate common names) and a country query parameter (to narrow results by nationality or country of office).
Read the scored response. Unlike the standard screening envelope, the PEP response returns similarity scores rather than a binary sanctioned/flagged verdict — review the score alongside the matched record to decide how to proceed.

curl "https://api.compliapi.com/api/v1/screen/pep/Jane%20Smith?birth_date=1970-05-14&country=NG" \  -H "Authorization: Bearer capi_..."

Pricing

The /screen/pep endpoint is priced higher than other screening endpoints — for both token-authenticated requests and x402 pay-per-request calls — because the underlying OpenSanctions PEP dataset is metered per query by the upstream provider. When using x402, the exact amount is always quoted in the 402 challenge you receive; always build your payment from that figure rather than assuming the standard rate.

Tips and limits

The birth_date and country arguments are optional but recommended when screening common names, since the PEP dataset covers many individuals with similar names.
The screen_pep MCP tool exposes the same endpoint for AI agents, with the same name, birth_date, and country arguments.
The /screen/pep endpoint does not accept a ?lists= filter, because it proxies a single upstream dataset rather than the multi-list registry used by other screening endpoints.
PEP hits do not constitute sanctions hits. If your workflow requires both checks, run /screen/pep alongside a standard screening call such as /screen/id or /screen/email.