# Token Supply Lookup for Base Tokens

> Token Supply Lookup for Base Tokens is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Returns the total supply of any Base token, both raw and decimals-scaled, along with its name and symbol.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/token-supply
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/token-supply-lookup-for-base-tokens-ae728a35
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wmUIT7MTX-0XSsNOIkJf5

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 token-supply-lookup-for-base-tokens-ae728a35
```

Example prompt: What's the total supply of the Base token at contract address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 — give me both the raw number and the human-readable scaled amount with the token name and symbol?

## When to prefer this

Use this endpoint when you need quick, reliable total supply data for a Base ERC-20 token, especially when you also need the human-readable scaled value alongside raw supply. Prefer it over generic blockchain RPC calls when you want decimals handling and token metadata (name, symbol) in a single call. It is purpose-built for Base and handles the decimals-scaling edge case explicitly with a warning flag.

## Known failure modes

- Non-token contract address returns found:false with no supply data
- Contract without a declared decimals() function causes the API to assume 18 decimals and sets an assumed-decimals flag, which may produce misleading scaled supply figures
- Invalid or malformed contract address may result in an error response
- Token exists but has non-standard supply methods may not return correct data
- Network or RPC errors on Base may cause timeouts

## How this service works

🆕 totalSupply for any Base token, returned raw and scaled by its decimals, alongside the name and symbol. When a contract doesn't declare decimals the answer assumes 18 and marks that it assumed — a silent guess here quietly moves every downstream number by orders of magnitude. Non-token addresses answer found:false.

## Output

Returns a JSON object with: found (boolean indicating if address is a token), token name, symbol, raw total supply, decimals (with a flag if 18 was assumed rather than declared), and the supply scaled by decimals. Non-token addresses return found:false.

## 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": [
      "token"
     ],
     "properties": {
      "token": {
       "type": "string",
       "description": "Token contract"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/token-supply-lookup-for-base-tokens-ae728a35/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)
