# BlockchainAnalysis.io Oracle — Wallet & Transaction Compliance Screener

> BlockchainAnalysis.io Oracle — Wallet & Transaction Compliance Screener is a paid API for AI agents from blockchainanalysis.io, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Screen a blockchain address or transaction against regulatory risk models across 34 jurisdictions and 52 blockchains, returning a scored compliance verdict with confidence level.

## Facts

- Endpoint: POST https://blockchainanalysis.io/api/x402/oracle
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockchainanalysis-io-oracle-wallet-transaction-compliance-screener-93ec0e13
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FnujpNN9AQxSYr6bcOx7s

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 blockchainanalysis-io-oracle-wallet-transaction-compliance-screener-93ec0e13 -d '<json body>'
```

Example prompt: Can you run a compliance oracle check on Ethereum address 0x28c6...1d60 and tell me the risk score and whether it's safe to transact with?

## When to prefer this

Choose this endpoint when you need a single, authoritative compliance oracle verdict with a numeric confidence score for a specific blockchain address or transaction, especially when operating across multiple chains (up to 52) and needing regulatory context across a broad set of jurisdictions (up to 34). Prefer this over generic blockchain explorers when you need structured AML/sanctions scoring rather than raw transaction data, and when your workflow requires a pay-per-call model without subscription overhead.

## Known failure modes

- Invalid or malformed blockchain address returns an error verdict
- Unsupported chain identifier causes a bad-request error
- Insufficient payment (less than $1 USDC via x402) results in a 402 Payment Required response
- Address not yet indexed on a newly supported chain may return low-confidence or unavailable result
- Rate limiting or network timeout may cause delayed or failed responses

## How this service works

Screen wallets, analyze exchange accounts, and monitor transactions with regulatory context across 34 jurisdictions and 52 blockchains.

## Output

A JSON object containing the oracle tool name, the target chain, the screened address, the payment method, and a natural-language verdict string indicating safe/risky status along with a numeric score out of 100 and a confidence level, plus a structured verdict object with detailed regulatory findings.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "oracle",
  "chain": "eth",
  "result": "Oracle verdict: safe (score 90/100, high confidence) { ...verdict }",
  "address": "0x28c6...1d60",
  "paidVia": "x402"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockchainanalysis-io-oracle-wallet-transaction-compliance-screener-93ec0e13/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from blockchainanalysis.io](https://www.zero.xyz/host/blockchainanalysis.io/llms.txt)