# Strale Web3 Counterparty Due Diligence

> Strale Web3 Counterparty Due Diligence is a paid API for AI agents from api.strale.io, paid per call via x402, $0.162/call, status unknown (last checked 2026-09-15).

Performs sanctions, PEP, and blockchain risk due diligence on a crypto wallet address, with optional entity name check, across supported chains

## Facts

- Endpoint: POST https://api.strale.io/x402/v2/solutions/web3-counterparty-dd
- Price: $0.162/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-web3-counterparty-due-diligence-cd6335f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0pj3NNLP-e8b3alOXTJCH

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 strale-web3-counterparty-due-diligence-cd6335f1 -d '<json body>'
```

Example prompt: Can you run a sanctions and PEP check on this Ethereum wallet — 0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD — and let me know if there's any counterparty risk before I proceed with the transfer?

## When to prefer this

Choose this endpoint when you need blockchain-native AML/KYC compliance checks that combine on-chain wallet investigation with traditional sanctions and PEP screening. It is especially suited for pre-transaction due diligence in DeFi, crypto OTC, or Web3 payment workflows where an auditable, cryptographically hashed compliance record is required. Prefer this over generic sanctions APIs when the subject is a wallet address rather than a traditional legal entity.

## Known failure modes

- Invalid wallet address format returns a validation error
- Unsupported chain_id returns an error indicating the chain is not covered
- Wallet not found on-chain may return limited or no screening data
- Network timeout or upstream data provider unavailability results in a 5xx error
- Malformed request body (missing wallet_address) returns a 400 bad request

## How this service works

The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.

## Output

Returns a due diligence report on the wallet address including sanctions list matches (e.g. OFAC, EU, UN), PEP status, and overall counterparty risk assessment. Each call includes a cryptographic audit record with chain hashing for compliance traceability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain_id": {
   "type": "string",
   "description": "Chain ID, default 1 (Ethereum)"
  },
  "entity_name": {
   "type": "string",
   "description": "Entity or person name for sanctions/PEP check (if known)"
  },
  "wallet_address": {
   "type": "string",
   "description": "Wallet address to investigate (0x...)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-web3-counterparty-due-diligence-cd6335f1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)