# Base Address Safety Check

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

Checks whether a given Base network address (EOA or contract) is safe or flagged for risk/malicious activity

## Facts

- Endpoint: POST https://true402.dev/api/v1/base/address-safety
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-address-safety-check-b4d0483e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_imr79fVZcGDyUkXQUIG24

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 base-address-safety-check-b4d0483e -d '<json body>'
```

Example prompt: Can you check if this Base address is safe before I send funds to it — 0x4a2f6Ae7a1099abe3B1C1A1234567890AbCdEf12?

## When to prefer this

Use this endpoint when you need a quick, per-call safety check on a specific Base network address before executing a transaction, integrating a new counterparty wallet, or interacting with an unknown smart contract. Ideal for agents automating DeFi workflows, payment routing, or airdrop screening on Base chain where address vetting is critical.

## Known failure modes

- Invalid or malformed 0x address returns an error
- Non-Base chain specified returns unsupported chain error
- Network timeout or service unavailability
- Address not found or no data available for very new addresses
- Payment failure via HTTP 402 if USDC wallet is not funded

## 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 Base address, potentially including risk flags, classification (EOA vs contract), and any known malicious activity or threat indicators associated with the address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "Chain to check; only 'base' is supported (default)"
  },
  "address": {
   "type": "string",
   "description": "Any address (0x…) on Base — 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/base-address-safety-check-b4d0483e/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)