# Wallet Risk Check

> Wallet Risk Check is a paid API for AI agents from mcp.dropenginehq.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-02).

Checks a Base blockchain wallet or contract address for counterparty risk signals before an agent sends funds, accepts payments, or grants approvals

## Facts

- Endpoint: POST https://mcp.dropenginehq.com/api/check-wallet?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wallet-risk-check-7900d538
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zBCCmH47f5ELAPWs6wNTJ

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 wallet-risk-check-7900d538 -d '<json body>'
```

Example prompt: Before I send payment, run a risk check on the Base wallet address 0xAbC1234567890abcdef1234567890ABCDEF12345 on the base mainnet and tell me if it's safe to proceed.

## When to prefer this

Use this endpoint when an AI agent needs to programmatically screen a Base blockchain address before any financial interaction — sending funds, accepting payments, or granting token approvals. Prefer this over manual lookups when you need machine-readable risk signals and a structured recommendation suitable for automated decision-making. Particularly valuable in agentic payment pipelines where the agent must gate transactions without human review.

## Known failure modes

- Invalid address format (not a valid 0x 40-hex-character address) returns validation error
- Unsupported chain value (anything other than 'base' or 'base-sepolia') returns error
- Address not found or no on-chain history may return low-confidence result with limited signals
- Intelligence provider not configured means sanctions/malicious lists are not checked
- Network timeout or provider unavailability returns service error
- Payment failure (insufficient USDC balance) blocks the call at the x402 layer

## How this service works

Checks a public Base wallet or contract address for counterparty risk before an autonomous agent sends funds, accepts payments, grants approvals, or interacts with it. Returns on-chain account metadata, machine-readable risk signals, confidence, and a conservative recommendation. Sanctions and malicious-address matches are unknown unless a trusted intelligence provider is configured. Never send private keys or seed phrases.

## Output

Returns on-chain account metadata for the address, machine-readable risk signals (e.g. contract vs EOA, activity patterns), a confidence score, and a conservative yes/no/review recommendation. Sanctions and malicious-address matches are included only if a trusted intelligence provider is configured.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "base-sepolia"
   ],
   "type": "string"
  },
  "address": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/wallet-risk-check-7900d538/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp.dropenginehq.com](https://www.zero.xyz/host/mcp.dropenginehq.com/llms.txt)