# AgentPay Sanctions Screening

> AgentPay Sanctions Screening is a paid API for AI agents from agentpay.help, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Screens a person or entity name against global sanctions lists and returns a sanctioned status, match score, and matched lists.

## Facts

- Endpoint: POST https://agentpay.help/v1/sanctions-screen
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentpay-sanctions-screening-9993d81b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IRDdkaiIGvKgJCq83fqmB

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentpay-sanctions-screening-9993d81b -d '<json body>'
```

Example prompt: Can you run a sanctions check on 'Viktor Petrov' as a person and tell me if they appear on any sanctions lists?

## When to prefer this

Choose this endpoint when you need a lightweight, no-account, pay-per-use sanctions screening API that accepts a name and optional type, and returns an immediate pass/fail result with a match score. Ideal for AI agents automating compliance checks without setting up a full KYC platform subscription. Best for one-off or low-volume checks billed in USDC micropayments.

## Known failure modes

- Missing or empty name field returns a validation error
- Ambiguous or very common names may return low match scores even if a sanctioned individual exists
- Service unavailable or payment failure via x402 returns a 402 Payment Required response
- Name transliterations or alternate spellings may not match sanctioned entries

## How this service works

Pay-per-call AI services via the 402 Payment Required protocol. No accounts, no API keys — just USDC on Base.

## Output

Returns a JSON object indicating whether the screened name is sanctioned (boolean), a numerical match score (0–1 indicating confidence of a match), and an array of sanctions lists on which the name was found (empty if none).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "Person or entity name"
  },
  "type": {
   "enum": [
    "person",
    "entity"
   ],
   "type": "string",
   "description": "Screening type, optional"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "lists": [],
  "sanctioned": false,
  "match_score": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentpay-sanctions-screening-9993d81b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentpay.help](https://www.zero.xyz/host/agentpay.help/llms.txt)