# ChainRay Address Labels

> ChainRay Address Labels is a paid API for AI agents from chainray.online, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Resolves human-readable labels for blockchain wallet or contract addresses (e.g. exchange names, protocol names, known entities)

## Facts

- Endpoint: GET https://chainray.online/address-labels/:var1
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainray-address-labels-7d091eef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MLw9cR8nSpkhWFfBJPpqI

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 chainray-address-labels-7d091eef
```

Example prompt: Can you look up the label for the address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum — I want to know if it's associated with a known entity like an exchange or protocol?

## When to prefer this

Use this endpoint when you need to enrich a raw blockchain address with a human-readable identity or entity name, especially for display, audit trails, compliance checks, or understanding counterparties in on-chain transactions. Prefer this over a full address report when you only need the label/identity, not full transaction history or analytics.

## Known failure modes

- Address not found in label database — returns empty or null label
- Invalid address format — returns 400 or validation error
- Unsupported chain parameter — returns error or defaults to a specific network
- Rate limiting or payment failure — returns 402 or 429
- Network timeout or service unavailability — returns 5xx

## How this service works

ChainRay /address-labels

## Output

Returns a human-readable label or entity name associated with the given blockchain address, such as an exchange name, DeFi protocol, known wallet owner, or entity category. May include classification metadata like whether it is a contract, EOA, exchange, bridge, or other known entity.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "Blockchain network"
      },
      "address": {
       "type": "string",
       "description": "Wallet or contract address"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainray-address-labels-7d091eef/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chainray.online](https://www.zero.xyz/host/chainray.online/llms.txt)