x402 sanctions screening quickstart

Inspect the challenge for free before authorizing any payment. No API key is required on this route.

1. Request the payment contract

curl -i 'https://sanctionsai.dev/x402/sanctions?name=ACME'

An unsigned request returns HTTP 402, not a screening result. Decode the base64 JSON in the Payment-Required header. Check the amount, asset, network and payTo address before signing. The standard price is 50000 atomic USDC units ($0.05) on Base (eip155:8453); the returned challenge is authoritative.

2. Authorize and retry

Use an x402 v2-compatible client and a wallet you control with sufficient USDC on Base. The client signs a payment authorization and retries the same request with a Payment-Signature header. Do not send a separate manual transfer. Never paste private keys into this site.

curl -i 'https://sanctionsai.dev/x402/sanctions?name=ACME' \
  -H 'Payment-Signature: <base64-signed-payment-authorization>'

The placeholder is not a valid signature. The server verifies and settles the authorization through its facilitator before screening. A rejected payment returns 402, not a successful screen.

3. Inspect the result

A successful request returns HTTP 200, screening JSON (clean and matches), and a base64 JSON Payment-Response receipt. This page does not show a real payment or customer result.

Supply at least one of name, wallet or country. A signed request with no subject returns 400 before settlement. An unconfigured payment service returns 503. An unsigned challenge does not charge your wallet.

Screening is a control, not legal advice or a certification of compliance. A no-match result does not guarantee a counterparty is safe.

API documentation | Subscription options

By SanctionsAI team. Updated 2026-09-06.