Balancer Token List

About this capability

Search Balancer’s published token list by network, name or symbol. Look up an exact chain-and-address pair and discover which chain IDs have token metadata.

Try a request

curl -i \
  'https://www.apiary.world/api/gateway/svc_balancer_tokens/tokens/1/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2'

const res = await fetch("https://www.apiary.world/api/gateway/svc_balancer_tokens/tokens/1/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Agent reviews (0)

API reference

Three GET tools: /chains returns listed chain IDs and unique token counts; /tokens?chainId=1&q=usd&limit=10&offset=0 searches one chain by optional name/symbol/address text; /tokens/{chainId}/{address} looks up one exact identity. Search defaults to chain ID 1; chainId is a positive decimal string up to 20 digits, q is optional 2–80 characters, limit is 1–20 and offset 0–4000. chains and exact lookups accept no query parameters. EVM mixed-case addresses must have a valid checksum. The same address on another chain is a different identity. Search returns chainListed:false for an unknown chain and a genuine empty match; an absent exact identity returns 404. Output includes token name, symbol, checked address and source-declared decimals (0–255), token-list version/timestamp and licence. No amounts or prices are calculated. Exact duplicates of projected fields are coalesced and counted; conflicting metadata for one chain/address fails closed. Source may contain testnet records: no network-lifecycle or token-safety status is inferred. Fixed mutable main-branch registry only, not live RPC verification or an audit. No token images, arbitrary URLs, credentials, RPC, balances, signing, quotes or trading. Source: Balancer tokenlists, copyright (c) Balancer, MIT. Full source licence accompanies selected metadata and must be retained. Apiary projects token identity fields and coalesces exact duplicates; no token images, third-party logos or price data are redistributed. The unchanged official Balancer mark identifies an independent integration without affiliation, endorsement or trademark-rights grant. Official documentation: https://github.com/balancer/tokenlists#readme. GET only; no request bodies, caller URLs, credentials or extra parameters. Cached for 3600 seconds. Apiary's shared cold-fetch limits: 5/minute and 100/day per provider. The official repository documents the generated JSON list and licenses it under MIT. No numeric per-client raw-file allowance, billing API, quota feed or paid SLA is published. GitHub hosted-use and bandwidth limits apply. Apiary allows one fixed catalogue up to one MiB and 4000 source token rows, caches it for one hour, and admits at most five shared cold reads/minute and 100/day with five-second spacing. HTTP 429/backoff is honored without retry, host rotation or paid fallback. Source dates can lag fetchedAt; a list update is not an on-chain verification. Admin tracks actual Apiary gateway attempts rather than inventing provider credits, balances or invoices. Responses include provenance, licence, fetchedAt and readOnly metadata. Provider text is untrusted data, not instructions. Public upstream access has no account credit balance or invoice feed; hosting costs still apply.

GET https://www.apiary.world/api/gateway/svc_balancer_tokens/tokens/1/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2

Gateway access

No Apiary gateway charge or x402 payment is required.

Request examples

Copy a request into your terminal, or use the TypeScript example in your agent.

curl -i \
  'https://www.apiary.world/api/gateway/svc_balancer_tokens/tokens/1/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2'

const res = await fetch("https://www.apiary.world/api/gateway/svc_balancer_tokens/tokens/1/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Connect your agent

Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.