# PayPerByte Sanctions Screening Oracle

> PayPerByte Sanctions Screening Oracle is a paid API for AI agents from x402.payperbyte.io, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-13).

Screens a crypto address or counterparty name against OFAC SDN and Consolidated sanctions lists, returning a BLOCK/PASS verdict with EIP-712 cryptographic attestation

## Facts

- Endpoint: POST https://x402.payperbyte.io/feeds/sanctions-screen
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payperbyte-sanctions-screening-oracle-71aa1963
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SKJiTYRo6-h4y7mDkOrB2

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 payperbyte-sanctions-screening-oracle-71aa1963 -d '<json body>'
```

Example prompt: Before I send funds, can you screen the wallet address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 against the OFAC sanctions list and give me a signed attestation I can verify?

## When to prefer this

Choose this endpoint when you need a cryptographically attested, verifiable sanctions verdict that you can independently verify on-chain — not just a raw database query. It is ideal for DeFi applications, payment agents, and compliance workflows that require tamper-evident proof of which exact OFAC list version (SHA-256 anchored) was consulted and that the result was signed by the feed's own publisher key. Prefer this over generic sanctions APIs when you need EIP-712 receipts for audit trails, on-chain verifiability, or when operating in trustless agent pipelines where data provenance must be cryptographically proven rather than assumed.

## Known failure modes

- Missing both address and name fields — API returns 400 requiring at least one of address or name
- Invalid address format (not 0x+40-hex or recognized digital-currency format) — rejected at input validation
- Payment failure via x402 protocol — endpoint returns 402 Payment Required if USDC payment is not attached
- OFAC list temporarily stale — stale:true flag in list_state indicates the list could not be refreshed
- Attestation signer mismatch — if recovered signer does not match expected publisher key, data may be tampered
- Name with fewer than 2 characters or more than 256 characters — rejected by minLength/maxLength constraints

## How this service works

Know-Your-Agent counterparty screening — sanctions pillar. Signed OFAC SDN + Consolidated screen on an address or name, pinned to the exact list-state (date + sha256). Screens the counterparty you supply — not the calling agent's identity. Full scope: https://x402.payperbyte.io/feeds

## Output

A JSON object containing: a verdict field (BLOCK or PASS), a score, an array of reasons explaining any match (including the exact SDN entry number and list name), the exact OFAC list state screened against (source, published date, SHA-256 content hash, entry count, staleness flag), the methodology version, and an EIP-712 attestation block with the signer address, signature, payload hash, and domain details (chainId 421614 = Arbitrum Sepolia signing namespace). The signer can be recovered from the attestation to verify authenticity and tamper-evidence.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "maxLength": 256,
   "minLength": 2,
   "description": "Counterparty name (individual or entity). Screened exact + conservative fuzzy against primary and a.k.a. names in the SDN + Consolidated lists."
  },
  "chain": {
   "type": "string",
   "description": "Optional, informational only — the SDN annex pins addresses to currency symbols; chain never gates a hit."
  },
  "address": {
   "type": "string",
   "description": "Counterparty address: 0x+40-hex (EVM) or a digital-currency address. Checked against the OFAC SDN digital-currency annex."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "_note": "Excerpt of a real answer (live service, 2026-07-01); hash/signature elided, signals/consolidated trimmed. Every answer pins the exact OFAC list version (published date + sha256 + entry count) it was judged against. Screening signal, not legal advice. The EIP-712 receipt — domain chainId 421614 = Arbitrum Sepolia, a frozen signing namespace, not a settlement rail — proves who signed these exact bytes (authenticity + tamper-evidence), not that the screening result is correct. Recompute keccak256(canonical answer bytes) and recover the signer before acting.",
  "answer": {
   "v": "sanctions-screen/v1",
   "query": {
    "name": "Lazarus Group",
    "chain": null,
    "address": null
   },
   "score": 0,
   "reasons": [
    "name exactly matches OFAC SDN primary name \"LAZARUS GROUP\": entry #27307 \"LAZARUS GROUP\" [DPRK3] — list published 2026-06-30"
   ],
   "verdict": "BLOCK",
   "list_state": {
    "sdn": {
     "stale": false,
     "source": "OFAC SDN (Specially Designated Nationals and Blocked Persons)",
     "entry_count": 19129,
     "content_sha256": "a04efa5d60104ebd35fc08b6891811120d151bf37801fbd3c01e64380198f099",
     "published_date": "2026-06-30"
    }
   },
   "methodology": "ss-v1"
  },
  "attestation": {
   "domain": {
    "name": "BYTE Library",
    "chainId": 421614,
    "version": "1",
    "verifyingContract": "0x44729bB148F46d8Db509E47b0453edc271e06e95"
   },
   "signer": "0x344ECaCDe6566294c31397445c98b62a3EEEA456",
   "signature": "0x…",
   "payloadHash": "0x…"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payperbyte-sanctions-screening-oracle-71aa1963/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.payperbyte.io](https://www.zero.xyz/host/x402.payperbyte.io/llms.txt)