# JPYC Live Total Supply by Chain

> JPYC Live Total Supply by Chain is a paid API for AI agents from open-pay.jp, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Returns the live total supply of JPYC (Japan's yen-pegged stablecoin) for one or all supported chains (Polygon, Kaia, Avalanche, Ethereum), read directly from the token contracts at request time.

## Facts

- Endpoint: GET https://open-pay.jp/api/paid/usdc/jpyc/supply
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jpyc-live-total-supply-by-chain-28b8d02e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tKNaT7ktiKXMXZPYm4F9U

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 jpyc-live-total-supply-by-chain-28b8d02e
```

Example prompt: What is the current total supply of JPYC across all chains — Polygon, Kaia, Avalanche, and Ethereum? Give me the supply, block number, and contract address for each.

## When to prefer this

Use this endpoint when you need real-time, on-chain JPYC token supply data directly from the smart contracts, optionally filtered by a specific supported chain. Prefer this over cached or aggregated sources when freshness and block-level accuracy matter, such as for market cap calculations, tokenomics monitoring, or cross-chain supply reconciliation.

## Known failure modes

- Unsupported chain value returns a validation error
- RPC node unavailability may cause timeout or incomplete data
- Payment failure (x402) blocks access if USDC is not provided
- Stale or slow block data if the underlying RPC is lagging

## How this service works

Read the current contract-reported JPYC totalSupply on Polygon, Kaia, Avalanche or Ethereum, with the token contract address and the block number observed at request time. Use for periodic supply monitoring, cross-chain comparison, or verifying a current JPYC supply figure before citing it. Not for market price, reserve backing, circulating-supply analysis, or financial advice.

## Output

A JSON response containing, for each queried chain, the JPYC total supply (as a numeric value), the block number at which the supply was read, and the token contract address on that chain. If the optional 'chain' parameter is omitted, results for all four chains (Polygon, Kaia, Avalanche, Ethereum) are returned.

## 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"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "chain": {
       "enum": [
        "polygon",
        "kaia",
        "avalanche",
        "ethereum"
       ],
       "type": "string",
       "description": "Chain to query. Omit to query all supported chains. Supported values: polygon, kaia, avalanche, ethereum."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "schemaVersion",
      "token",
      "generatedAt",
      "notice",
      "termsUrl",
      "items"
     ],
     "properties": {
      "items": {
       "type": "array",
       "items": {
        "oneOf": [
         {
          "type": "object",
          "required": [
           "chain",
           "chainId",
           "contract",
           "status",
           "blockNumber",
           "totalSupply",
           "totalSupplyFormatted"
          ],
          "properties": {
           "chain": {
            "enum": [
             "polygon",
             "kaia",
             "avalanche",
             "ethereum"
            ],
            "type": "string"
           },
           "status": {
            "type": "string",
            "const": "ok"
           },
           "chainId": {
            "type": "integer",
            "minimum": 1
           },
           "contract": {
            "type": "string",
            "pattern": "^0x[a-fA-F0-9]{40}$"
           },
           "blockNumber": {
            "type": "string",
            "pattern": "^[0-9]+$"
           },
           "totalSupply": {
            "type": "string",
            "pattern": "^[0-9]+$",
            "description": "Atomic JPYC amount with 18 decimals."
           },
           "totalSupplyFormatted": {
            "type": "string",
            "pattern": "^[0-9]+(\\.[0-9]+)?$"
           }
          },
          "additionalProperti
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jpyc-live-total-supply-by-chain-28b8d02e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from open-pay.jp](https://www.zero.xyz/host/open-pay.jp/llms.txt)