# Webacy OFAC/Sanctions Screening API

> Webacy OFAC/Sanctions Screening API is a paid API for AI agents from api.webacy.com, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-31).

Screens a blockchain wallet address against OFAC and sanctions lists, returning a sanctions status and related compliance signals.

## Facts

- Endpoint: GET https://api.webacy.com/sanctioned/:address?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webacy-ofac-sanctions-screening-api-9de342e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J6SSS79sFtTmrF6ZSVZCf

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 webacy-ofac-sanctions-screening-api-9de342e9
```

Example prompt: Before I send funds, can you run an OFAC sanctions check on the Ethereum wallet address 0xABCD1234... to make sure it's clean?

## When to prefer this

Use this endpoint when you need a focused, compliance-grade OFAC/sanctions check on a single wallet address before executing a transaction, onboarding a user, or approving a counterparty. It is purpose-built for regulatory screening workflows rather than general risk scoring — prefer this over broader risk analysis endpoints when the specific question is sanctions/blacklist status. Ideal for DeFi protocols, payment processors, and treasury management systems with AML/KYC obligations.

## Known failure modes

- Invalid or malformed wallet address returns an error or unexpected result
- Missing or invalid `chain` query parameter causes a 400 or validation error
- Unsupported chain identifier returns an error
- Rate limiting or payment failure (x402) prevents the call from completing
- Address not found on the specified chain may return an ambiguous result
- Network timeouts from upstream sanctions data providers

## How this service works

OFAC / sanctions screening for a wallet address. Compliance-sensitive callers should gate on `sanctions_status === "clean"`, not `is_sanctioned === false`.

## Output

Returns a sanctions screening result for the queried wallet address, including a `sanctions_status` field (e.g. 'clean' or 'sanctioned') and an `is_sanctioned` boolean flag. Compliance-sensitive callers should rely on `sanctions_status === 'clean'` as the authoritative gate rather than the boolean alone.

## 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",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "properties": {
      "address": {
       "type": "string",
       "description": "Wallet address to screen"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "required": [
      "chain"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "Blockchain network, e.g. eth, bsc, pol, arb, opt, base, sol"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/webacy-ofac-sanctions-screening-api-9de342e9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.webacy.com](https://www.zero.xyz/host/api.webacy.com/llms.txt)