# Obol EVM Address Risk Profile / Wallet Security Check

> Obol EVM Address Risk Profile / Wallet Security Check is a paid API for AI agents from obol-x402.fly.dev, paid per call via x402, $0.1/call, status down (last checked 2026-09-15).

Returns a risk profile and safety verdict for any EVM address on Base, including contract vs EOA detection, transaction activity, ETH balance, dormancy flags, proxy detection, and a risk score.

## Facts

- Endpoint: POST https://obol-x402.fly.dev/v1/evm/address/:address
- Price: $0.1/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-evm-address-risk-profile-wallet-security-check-81b3122a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d8FKEVCm71kqrPxw7bdJW

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 obol-evm-address-risk-profile-wallet-security-check-81b3122a -d '<json body>'
```

Example prompt: Before I send 500 USDC to 0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD, can you run a risk check on that address — I want to know if it's a contract or regular wallet, how active it is, and whether it's flagged as high risk?

## When to prefer this

Choose this endpoint when an AI agent needs to assess counterparty risk before executing a payment or approving a transaction on Base — especially when you want on-chain behavioral signals (activity level, contract type, dormancy, proxy detection) combined into a single risk verdict. Prefer this over generic blockchain explorers when you need a machine-readable safety score rather than raw blockchain data.

## Known failure modes

- Invalid or malformed EVM address returns a 400 error
- Address not found or never used on Base may return minimal data or a new-wallet flag
- Payment not included or insufficient USDC triggers a 402 Payment Required response
- Network or RPC issues fetching on-chain data may result in a 503 or timeout
- Ed25519 signature verification failure if the response was tampered in transit

## Output

A JSON object containing the address risk verdict (safe/risky/unknown), risk score, contract vs EOA classification, transaction count, ETH balance, flags for brand-new or dormant wallets, proxy contract detection, and on-chain behavioral signals — all cryptographically signed with Ed25519 for independent verification.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-evm-address-risk-profile-wallet-security-check-81b3122a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from obol-x402.fly.dev](https://www.zero.xyz/host/obol-x402.fly.dev/llms.txt)