# ChainRay Token Supply

> ChainRay Token Supply 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).

Retrieves the token supply (circulating, total, or max) for a given token contract address on a specified blockchain network

## Facts

- Endpoint: GET https://chainray.online/token-supply/: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-token-supply-b2d9df3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nTxFp2fSqjHsIGj2r8bte

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-token-supply-b2d9df3e
```

Example prompt: What's the token supply for the contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum?

## When to prefer this

Use this endpoint when you need on-chain token supply metrics for a specific contract address across any of 46+ supported blockchains. Prefer this over general blockchain explorers when building automated agent workflows that need programmatic, pay-per-call access to token economics data without API key management.

## Known failure modes

- Invalid or non-existent contract address returns error or empty result
- Unsupported chain identifier causes a 400 or 404 error
- Missing required 'address' query parameter returns validation error
- Network timeout or upstream RPC node unavailability causes 503
- Contract address exists but is not a token contract returns null or zero supply

## How this service works

ChainRay /token-supply

## Output

Returns token supply data for the queried contract address, including circulating supply, total supply, and/or max supply figures for the specified blockchain network.

## 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-token-supply-b2d9df3e/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)