Token Metadata

blockchain

Serving

Canonical token metadata across 6 EVM chains: symbol, decimals, name, logo, and token-list provenance. POST /v1/token with {address, chain_id} and get one JSON object back. Deterministic per token-list vintage. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/token-metadata/v1/token
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/token-metadata/v1/token \
  -H 'content-type: application/json' \
  -d '{"address":"0xdAC17F958D2ee523a2206206994597C13D831ec7","chain_id":1}'

Example response

The response this call returned, captured 2026-09-21 23:49:42 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "token-metadata",
    "schemaCheck": "unchecked"
  },
  "data": {
    "address": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
    "chain_id": 1,
    "symbol": "USDT",
    "decimals": 6,
    "on_chain_read": true,
    "list_provenance": "adapter pending (token-list gateways flaky from this seat; verified live 09-16)",
    "as_of": "2026-09-21T23:49:41Z",
    "source": "publicnode RPC eth_call symbol()/decimals() (live read)"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Token Metadata accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/token`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "A token to look up.",
  "properties": {
    "address": {
      "type": "string",
      "description": "Token contract address, 0x-prefixed."
    },
    "chain_id": {
      "type": "integer",
      "description": "EVM chain id (default 1)."
    }
  },
  "required": [
    "address"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/token, a JSON object with symbol, decimals, name, logo, and token-list provenance. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}