# Ethereum Address Safety Checker

> Ethereum Address Safety Checker is a paid API for AI agents from true402.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Checks whether an Ethereum address (EOA or contract) is safe or flagged as risky/malicious.

## Facts

- Endpoint: POST https://true402.dev/api/v1/ethereum/address-safety
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ethereum-address-safety-checker-6207f9cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_b8da2Ej74YfqI5VHXn5oI

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 ethereum-address-safety-checker-6207f9cd -d '<json body>'
```

Example prompt: Can you check if the Ethereum address 0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD is safe before I interact with it?

## When to prefer this

Use this endpoint when you need a quick, per-call safety check on an Ethereum address before executing a transaction, interacting with a smart contract, or accepting funds — especially in automated agent workflows where wallet-native micropayments via x402 are already in use and no subscription is needed.

## Known failure modes

- Invalid or malformed Ethereum address (non-0x format) returns an error
- Address not found or zero-data address may return minimal or inconclusive results
- Only Ethereum mainnet is supported; passing a different chain identifier may return an error or default behavior
- Payment failure via HTTP 402 if USDC balance is insufficient

## How this service works

The machine-native marketplace. Wallet = identity. Pay per call with HTTP 402.

## Output

A JSON object describing the safety status of the queried Ethereum address, including risk flags, classification (EOA or contract), and any known malicious activity or exploit associations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "Chain to check; only 'ethereum' is supported on this endpoint (default)"
  },
  "address": {
   "type": "string",
   "description": "Any address (0x…) on Ethereum — an EOA or a contract"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "risk": {
   "type": "string",
   "description": "low | medium | high | critical"
  },
  "type": {
   "type": "string",
   "description": "eoa | contract"
  },
  "flags": {
   "type": "array",
   "description": "risk flags raised"
  },
  "score": {
   "type": "number",
   "description": "0–100 structural safety score"
  },
  "address": {
   "type": "string"
  },
  "txCount": {
   "type": "number"
  },
  "contract": {
   "type": "object",
   "description": "null for an EOA; else { isToken, erc20, ownership, mintable, isProxy, implementation }"
  },
  "ethBalance": {
   "type": "string"
  },
  "usdcBalance": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ethereum-address-safety-checker-6207f9cd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from true402.dev](https://www.zero.xyz/host/true402.dev/llms.txt)