GET
/
v1
/
evm
/
token-info
/
{uri}
Get EVM token information for a specified contract address (or the native token), on any chain.
curl --request GET \
  --url https://api.sim.dune.com/v1/evm/token-info/{uri} \
  --header 'X-Sim-Api-Key: <x-sim-api-key>'
{
  "contract_address": "native",
  "tokens": [
    {
      "chain": "ethereum",
      "chain_id": 1,
      "price_usd": 12.34,
      "symbol": "ETH"
    }
  ]
}
Tokeninfo Sv The Tokens API provides metadata and realtime pricing information for native and ERC20 tokens on supported EVM blockchains. The API returns:
  • Token metadata (symbol, name, decimals)
  • Current USD pricing information
  • Supply information
  • Logo URLs when available
The ?chain_ids query parameter is mandatory. To learn more about this query parameter, see the Supported Chains page.

Token Prices

Sim looks up prices onchain. We use the most liquid onchain pair to determine a usd price. We return the available liquidity in pool_size as part of the response.

Historical prices

You can request 24 hour point-in-time prices by adding the optional historical_prices query parameter. Use whole numbers only, from 1 to 24. You can request up to three offsets. For example, historical_prices=24 returns the price 24 hours ago. historical_prices=1,6,24 returns prices 1 hour ago, 6 hours ago, and 24 hours ago.
The historical_prices query parameter is currently supported only on the EVM Token Info and EVM Balances endpoints.
When set, each token object includes a historical_prices array with one entry per offset:
{
  "tokens": [
    {
      "chain": "base",
      "symbol": "ETH",
      "price_usd": 3897.492219,
      "historical_prices": [
        { "offset_hours": 24, "price_usd": 3816.557286 },
        { "offset_hours": 6,  "price_usd": 3914.205613 },
        { "offset_hours": 1,  "price_usd": 3898.926195 }
      ]
    }
  ]
}
Percent changes are not returned. You can compute your own percentage differences using the current price_usd and the values in historical_prices[].price_usd.

Pagination

This endpoint uses cursor-based pagination. You can use the limit parameter to define the maximum page size. Results might at times be less than the maximum page size. The next_offset value is included in the initial response and can be utilized to fetch the next page of results by passing it as the offset query parameter in the next request.
You can only use the value from next_offset to set the offset parameter of the next page of results. Using your own offset value will not have any effect.

Headers

X-Sim-Api-Key
string
required

Used for authenticating requests. Provide an API key with a purpose of Sim API. See Authentication.

Path Parameters

uri
string
default:0xd9aaec86b65d86f6a7b5b1b0c42ffa531710b6ca
required

The contract address of the token or 'native' for the native token of the chain

Query Parameters

chain_ids
string
default:8453
required

Either 'all' or a comma separated list of chain ids to get token info for

historical_prices

Request point-in-time prices within the last 24 hours. Accepts integer | integer[]. Provide whole numbers from 1 to 24, with a maximum of 3 time offsets (e.g. 24 or 1,6,24). When present, each token includes a historical_prices array with one entry per offset.

Required range: 1 <= x <= 24
limit
integer

This endpoint returns up to the number of supported chains. See Supported Chains to learn more.

Required range: x >= 0
offset
string

The offset to paginate through result sets; this is a cursor being passed from the previous response, only use what the backend returns here

Response

200
application/json

Successful Response

The response is of type object.