# Invoket Entity Screening — Sanctions & Watchlist Check

> Invoket Entity Screening — Sanctions & Watchlist Check is a paid API for AI agents from api.invoket.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Screens a company or person name against official sanctions and watchlists, returning deterministic match verdicts with provenance for pre-action compliance checks.

## Facts

- Endpoint: POST https://api.invoket.com/screen/entity
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-entity-screening-sanctions-watchlist-check-53c42a5a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tnnfnT1q_y3T0knVPpP62

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 invoket-entity-screening-sanctions-watchlist-check-53c42a5a -d '<json body>'
```

Example prompt: Before I wire the payment, screen 'Meridian Global Supplies Ltd' as a company registered in Iran — include weak alias matches in the verdict so I can review everything.

## When to prefer this

Choose this endpoint when an AI agent needs a deterministic, provenance-backed sanctions or watchlist verdict before executing a payment, onboarding a counterparty, or taking any regulated action. It is purpose-built for pre-action compliance hooks in agentic workflows, unlike general-purpose search or KYC APIs. Prefer it when you need exact match semantics with explicit weak/strong distinction, official source attribution in every response, and per-call pay-as-you-go pricing with no subscription overhead.

## Known failure modes

- Name too short or too long (outside 2–200 characters after whitespace collapse)
- Invalid country code (not ISO 3166-1 alpha-2) returns validation error
- Invalid birth_year outside 1800–2100 range
- Payment failure via x402 protocol (402 response if funds unavailable)
- Empty or ambiguous name producing no candidates — verdict may be clear with no hits
- List source temporarily unavailable — response may note reduced coverage

## How this service works

The checks your agent runs before it acts: verify a bank account, a phone number, a law in force, the weather or a vehicle — computed from official sources, with provenance in every response. You only pay for answers.

## Output

Returns a structured verdict (clear/hit/review) for the screened name, a hits[] array with every matching record including alias type and match strength, the official source list with provenance details, and metadata indicating whether weak matches were included in the verdict. Each response includes enough context for an agent to make or block a downstream action.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "kind",
  "name",
  "country",
  "include_weak"
 ],
 "properties": {
  "kind": {
   "type": "string",
   "description": "Optional filter, 'person' or 'entity'. A filter only ever REMOVES candidates, and only on data the list published in a comparable form: an entity that publishes nothing, or publishes its country in plain words, stays a candidate - a false negative costs more than one candidate too many"
  },
  "name": {
   "type": "string",
   "description": "Company or person name to screen, 2 to 200 characters once whitespace is collapsed. Matched against every name each list publishes - primary names and aliases, strong and weak. No edit distance and no phonetics: matching is deterministic and its type is named in the answer"
  },
  "country": {
   "type": "string",
   "description": "Optional ISO 3166-1 alpha-2 filter on the country published by the list (nationality or place of registration)"
  },
  "birth_year": {
   "type": "string",
   "description": "Optional filter for persons, 1800 to 2100, matched with a one-year tolerance either side. Persons whose birth date the list does not publish are never removed by it"
  },
  "include_weak": {
   "type": "string",
   "description": "Whether weak matches (an alias the source itself flags as weak, or a partial token overlap) count towards the verdict; default false. It changes ONLY the verdict: weak matches are always returned in hits[], so you can judge what was set aside for you"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-entity-screening-sanctions-watchlist-check-53c42a5a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.invoket.com](https://www.zero.xyz/host/api.invoket.com/llms.txt)