Onchain Data
Token metadata
Resolve a contract address to a token’s symbol, decimals and supply. Priced per token.
Spot price
$0.0050per token
call-weighted across 26 of 38 priced endpoints
- Spread
- 150×
- cheapest to dearest
- Providers
- 28
- 33 hosts
- Endpoints
- 38
- 27 answered last probe
Where the offers sitLog scale. The shaded band is the middle half of the market, $0.0020 to $0.015.
$0.0010$0.150
Every supplier below carries its index against that rate: 100 is spot, 40 is 60% below it, 310 is 3.1× it. Spot is weighted by how often each endpoint is called, so one wallet listing forty near-identical endpoints cannot move it on listings alone. The cheapest offer here is $0.0010 and the dearest $0.150.
Canonical request
| address | string | Token contract address. |
| chain? | string | CAIP-2 chain id. |
Canonical response
| address | string | Contract address. |
| symbol | string | Token symbol. |
| name | string | Token name. |
| decimals | number | Decimal places. |
| total_supply? | number | Total supply. |
38 endpoints offering this capability, from 28 wallets
Reading this table
- Price is what the catalog carries for one unit, per token. It is a published figure, not a quote — read the live 402 before paying.
- Index is that price against the spot rate, so it moves only with price — there is no separate sort for it, because ordering by index and ordering by price are the same ordering.
- 30d calls and payers are the upstream catalog’s own counters for that endpoint, so they measure demand, not quality.
- Status is the last liveness probe. There is no latency or uptime column yet: a single probe outcome cannot support one, and inventing a percentage from it would be worse than leaving it out.
- Settled volume per endpoint is also absent, and cannot be derived — a settlement carries the payee wallet, not the endpoint that was called, so a wallet serving forty endpoints cannot be split between them. The provider wallet’s own record is one click away on each row.
- The canonical response above is the shape Roundhouse maps each provider onto. Field mappings per provider are not published yet; today the contract is the target, not a guarantee about any one endpoint’s payload.
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will pick the best provider of this capability over the free read API. No key, no account.
GET roundhouseai.io/unified.json?capability=token-metadata
Show the promptHide the prompt
Using Roundhouse, compare every x402 provider of Token metadata and pick one for me. Weigh the price per unit against whether the endpoint answered when last probed, and say what the cheapest option would cost against the median. curl -s 'https://roundhouseai.io/unified.json?capability=token-metadata' The canonical request and response in that document are the shape every provider is mapped onto. Before paying, check the provider's record and read the live 402: curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet on the offer you choose>' The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.