# VeraData LATAM Sanctions Screening

> VeraData LATAM Sanctions Screening is a paid API for AI agents from api.veradata.dev, paid per call via x402, $0.05/call, status down (last checked 2026-09-16).

Screens individuals or entities against Latin American sanctions and watchlists, returning structured compliance data with an audit hash

## Facts

- Endpoint: POST https://api.veradata.dev/sanctions
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/veradata-latam-sanctions-screening-7ba4d1a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qVM8X8k5Gtuv_bjJbhJuu

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 veradata-latam-sanctions-screening-7ba4d1a0 -d '<json body>'
```

Example prompt: Can you run a LATAM sanctions screening on a person named 'Carlos Mendoza' using a full-name entity type? I need the audit hash and the structured compliance result.

## When to prefer this

Choose this endpoint when you need comprehensive Latin American sanctions screening with an auditable result hash — particularly when your compliance workflow requires multi-list LATAM coverage rather than OFAC-only. The sibling OFAC-only endpoint is cheaper for first-pass US screening; use this endpoint when LATAM regulatory lists (e.g., Brazil COAF, Mexico SAT, Colombian UIAF) must be included.

## Known failure modes

- Missing required 'type' or 'method' fields in the input object returns a 400 validation error
- Invalid entity type or screening method value causes a schema rejection
- Payment failure or insufficient USDC balance results in a 402 Payment Required response and no data returned
- Network timeout if the LATAM data provider is slow to respond
- Empty or ambiguous entity name may return no matches without indicating a true negative with certainty

## How this service works

Global sanctions screening: OFAC SDN + UN + EU + UK consolidated lists (59,000+ entries). EU AI Act Art.12/13 audit trail.

## Output

A JSON response containing a structured LATAM sanctions result (match status and relevant data) along with a SHA-256 audit hash for record-keeping and compliance audits.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "method": {
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/veradata-latam-sanctions-screening-7ba4d1a0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.veradata.dev](https://www.zero.xyz/host/api.veradata.dev/llms.txt)