API referenceLive
The tokens with the most liquidity (nodes) and the pools between them (edges): each pair's pools summed by depth and named by venue. size sets how many tokens.
Query Parameters
size?integer
How many tokens, in order of liquidity.
Range
20 <= value <= 800Default
400Response Body
application/json
application/json
curl -X GET "https://example.com/v1/map"{ "nodes": [ { "address": "string", "symbol": "string", "decimals": 0, "isStock": true, "liquidityUsd": 0, "priceUsd": 0, "holders": 0 } ], "edges": [ { "a": "string", "b": "string", "depthUsd": 0, "pools": 0, "venues": [ "string" ] } ], "asOf": 0, "source": "indexer"}Get the chain's last minute GET
The last sixty seconds in three figures: swaps, transactions and their dollar volume.
Get a transaction's token flow GET
How tokens moved in one transaction: every address it touches (`nodes`), every transfer in log order (`edges`), every swap on its pool with its maker, its owner and purpose, and the sender's net flows. A block not indexed yet answers `source: node` with the head and value alone: ask again shortly.