81trust / 100

Chain Token Metadata

by FiatDock in Onchain & crypto

x402 APIPassing, checked 3 h ago

ERC-20 token metadata on Base — name, symbol, decimals, total supply. Pay-per-call via x402. An empty body is answered for USDC on Base (the x402 settlement asset); send {"token":"0x…"} for any other token.

POST https://fiatdock.com/v1/chain/token-metadata

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
84 ms typical, 173 ms slowest 5%
Last check
3 h ago
Next check
any minute now

How to call it

POST https://fiatdock.com/v1/chain/token-metadata

Each call costs $0.002 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.

POST https://fiatdock.com/v1/chain/token-metadata
content-type: application/json

{
  "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}

Parameters

ParameterTypeRequiredDescription
tokenstringNoAn ERC-20 contract address (0x…) on Base. Omit the whole body to get USDC.

Example response

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

{
  "asOf": "2026-07-30T00:00:00.000Z",
  "contract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "decimals": 6,
  "name": "USD Coin",
  "network": "base",
  "symbol": "USDC",
  "totalSupply": "4200000000",
  "totalSupplyAtomic": "4200000000000000"
}

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.002.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://fiatdock.com/v1/chain/token-metadata' \
  -H 'content-type: application/json' \
  --data-raw '{"token":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'

# 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 - -X POST 'https://fiatdock.com/v1/chain/token-metadata' \
  -H 'content-type: application/json' \
  --data-raw '{"token":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}' \
  | 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ffiatdock.com%2Fv1%2Fchain%2Ftoken-metadata&method=POST
const res = await pay("https://fiatdock.com/v1/chain/token-metadata", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
  }),
});
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://fiatdock.com/v1/chain/token-metadata",
        json={
            "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        },
    )
    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
3 h agoPassed402173 ms$0.002
6 h agoPassed40252 ms$0.002
10 h agoPassed40284 ms$0.002
14 h agoPassed402349 ms$0.002