Supported networks¶

List supported chains is the live source of truth for your deployment — chains, their capabilities, and the Vector contract on each. Query it rather than hardcoding:

curl https://vector.example.com/supported-chains -H "api-key: $EDITH_API_KEY"

Each entry describes one chain:

{
  "id": 84532,
  "name": "base-sepolia",
  "displayName": "Base Sepolia",
  "explorerUrl": "https://sepolia.basescan.org",
  "vectorContract": "0x…",
  "chainType": "evm",
  "isTestnet": true,
  "nativeToken": { "symbol": "ETH", "name": "Sepolia Ether", "decimals": 18 },
  "features": { "gaslessSwaps": true, "crossChain": true, "permit2": true }
}

Feature flags¶

The features object tells you what each chain supports:

Flag	Meaning
`gaslessSwaps`	Gasless Permit2 execution is available.
`permit2`	Permit2 is deployed — required for gasless modes 2 and 3.
`crossChain`	The chain can be an endpoint of cross-chain routes.

Gate your UI on these flags per chain rather than assuming platform-wide capability.

Token catalog¶

Which tokens are quotable on a chain comes from the token endpoints:

List tokens — the catalog for one chain (note: chain_id query parameter).
Search tokens — free-text search by name or symbol, optionally scoped by chainId.

Tokens outside the catalog can still be quoted by address when liquidity exists; catalog entries additionally carry metadata (decimals, logoUrl, priceUsd on details) your UI can use.

Info

Chain availability is a deployment property — testnets and mainnets are enabled per environment. The id values are standard EVM chain ids and are safe to use as numbers.