80trust / 100

Chain Total Supply

by Token total supply in Onchain & crypto

x402 APIPassing, checked 4 h ago

The circulating total supply of an ERC-20, read from the token contract itself rather than from an aggregator, so it is the number the chain holds at the block you asked for. Returns the raw uint256 and the same figure formatted with the token's own decimals. A contract that does not implement totalSupply answers 422 rather than a fabricated zero. EVM chains: ethereum, base, polygon, arbitrum, optimism.

GET
https://agent402.tools/api/chain/total-supply
Price
$0.001
per call in USDC
Uptime
96.0%
last 30 days
Response time
192 ms
641 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

GET https://agent402.tools/api/chain/total-supply

Each call costs $0.001 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://agent402.tools/api/chain/total-supply?contract=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&network=base

Parameters

ParameterTypeRequiredDescription
contractstringYes0x ERC-20 token contract address
networkstringNoethereum | base | polygon | arbitrum | optimism (default base)

Example response

The provider's example. We can't check it without paying.

{
  "contract": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
  "decimals": 6,
  "network": "base",
  "totalSupply": "4182993441205067",
  "totalSupplyFormatted": "4182993441.205067"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://agent402.tools/api/chain/total-supply?contract=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&network=base'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://agent402.tools/api/chain/total-supply?contract=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&network=base' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fagent402.tools%2Fapi%2Fchain%2Ftotal-supply
const res = await pay("https://agent402.tools/api/chain/total-supply?contract=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&network=base");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://agent402.tools/api/chain/total-supply?contract=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&network=base")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402189 ms$0.001
8 h agoPassed402343 ms$0.001
12 h agoPassed402194 ms$0.001
16 h agoPassed402360 ms$0.001
21 h agoPassed402215 ms$0.001
Show 10 older checks
25 h agoPassed402188 ms$0.001
29 h agoTimed out---
33 h agoPassed402189 ms$0.001
36 h agoPassed402190 ms$0.001
40 h agoPassed402192 ms$0.001
44 h agoPassed402189 ms$0.001
2 days agoPassed402733 ms$0.001
2 days agoPassed402193 ms$0.001
2 days agoPassed402206 ms$0.001
2 days agoPassed402191 ms$0.001