# Address Identify: Wallet or Contract Classifier

> Address Identify: Wallet or Contract Classifier is a paid API for AI agents from apexfaucet.xyz, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-11).

Identifies whether an EVM (0x) or Base58 (Solana/X1) address is a wallet or contract, validates its checksum, checks for deployed code, detects proxy targets, and returns ERC-20 token metadata if applicable.

## Facts

- Endpoint: GET https://apexfaucet.xyz/api/x402/address-identify?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/address-identify-wallet-or-contract-classifier-10067969
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Tfp2yPCHvaimhF6LxdVS_

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 address-identify-wallet-or-contract-classifier-10067969
```

Example prompt: Can you tell me whether 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 is a wallet or a contract, and if it's a contract what ERC-20 token it represents — also confirm the checksum is correct?

## When to prefer this

Use this endpoint when you need a one-call answer about an unknown blockchain address — especially when you need both EIP-55 checksum validation AND on-chain code detection AND ERC-20 metadata in a single request across Ethereum, Base, and BNB Chain. It is particularly valuable before sending funds, interacting with a contract, or displaying token info for a user-supplied address. Prefer this over chain-specific RPC calls when multi-chain coverage and proxy detection matter. For Solana/X1 addresses it provides format validation without a chain read.

## Known failure modes

- Invalid address format not matching EVM 0x+40hex or Base58 pattern returns an error or ok:false
- Chains temporarily unavailable are listed in the `unread` field rather than failing the whole request
- NFT collections are not labeled as ERC-20 even if they have name/symbol
- Network timeouts on specific chains may result in partial data with affected chains in `unread`
- A valid checksum format with no deployed code returns wallet classification, not an error

## How this service works

APEX. What is this address? Pass ?address=. EVM 0x address: whether its EIP-55 checksum is valid and the correct checksummed form, then across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc, Robinhood Chain) whether code is deployed (contract or wallet, proxy target if any) and ERC-20 name, symbol, decimals and supply if it answers like a token. Base58 string: whether it decodes to a 32-byte Solana / X1 key size, no chain read. Unread chains appear in unread.

## Output

Returns a JSON object with an `ok` boolean, a `paid` amount in USDC, and a `data` object containing: EIP-55 checksum validity and corrected form for EVM addresses; per-chain results for Ethereum, Base, and BNB Chain indicating whether code is deployed (contract vs wallet); proxy target address if detected; ERC-20 name, symbol, decimals, and total supply if the contract responds as a token; and a list of chains that could not be read (`unread`). For Base58 inputs, confirms whether the string decodes to a valid 32-byte Solana/X1 key (no on-chain read).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "queryParams"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string",
       "pattern": "^(0x[0-9a-fA-F]{40}|[1-9A-HJ-NP-Za-km-z]{20,90})$",
       "description": "An EVM address (0x + 40 hex) or a base58 string such as a Solana / X1 address."
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "schema": {
  "type": "object",
  "properties": {
   "ok": {
    "type": "boolean"
   },
   "data": {
    "type": "object"
   },
   "paid": {
    "type": "number"
   }
  }
 },
 "example": {
  "ok": true,
  "data": {
   "ok": true,
   "kind": "evm",
   "note": "Code is read at the latest block of each chain; the same address can be a wallet…",
   "input": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "label": null,
   "chains": [
    {
     "note": "no contract code at this address on ethereum (an ordinary wallet, or an address …",
     "type": "wallet",
     "block": 26348559,
     "chain": "ethereum",
     "codeSize": 0
    }
   ],
   "unread": [],
   "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "checksumValid": true,
   "checksumStatus": "mixed case and it matches EIP-55"
  },
  "paid": 0.002
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/address-identify-wallet-or-contract-classifier-10067969/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apexfaucet.xyz](https://www.zero.xyz/host/apexfaucet.xyz/llms.txt)
