Supported Networks and Providers

xPath exposes network and token capabilities through its API. Applications should discover support at runtime instead of maintaining a static list.

Discover Supported Networks

Call GET /supported-chains:

const response = await fetch('https://api.xpath.rath.fi/supported-chains', {
  headers: { 'api-key': process.env.XPATH_API_KEY! },
})

const { data: chains } = await response.json()

Each chain includes:

• numeric chain ID and display name
• chain type and testnet flag
• explorer and public RPC URLs
• native token metadata
• xPath contract address
• feature flags for cross-chain routing, gasless swaps, and Permit2

Current Documented Networks

The current API specification documents:

Discover Tokens

Use:

• GET /tokens to list tokens for a chain or across supported chains
• GET /search-token to search by symbol, name, or address

Store token identity as (chainId, address), not symbol alone. The same symbol can represent unrelated assets or different contract deployments.

Provider Discovery

xPath selects DEX and bridge providers per quote. A route response exposes:

{
  "routeKind": "swapBridge",
  "providers": [
    {
      "name": "provider-key",
      "type": "bridge"
    }
  ],
  "path": [
    {
      "type": "bridge",
      "provider": {
        "name": "provider-key",
        "type": "bridge"
      }
    }
  ]
}

Provider availability is route-dependent. It can change based on:

• source and destination chains
• token pair and amount
• liquidity and bridge availability
• route mode
• provider health
• explicit include or exclude filters

Provider Policies

Use quote filters when your application has compliance, reliability, or UX constraints:

const params = new URLSearchParams({
  fromChain: '8453',
  toChain: '42161',
  fromToken,
  toToken,
  amount,
  sender,
  routeMode: 'suggested',
})

params.append('includeProvider', 'approved-provider')
params.append('excludeProvider', 'blocked-provider')

Do not hardcode a provider-specific execution payload. Always execute the transaction returned by xPath for the selected route.

Capability Checks

Before presenting a flow:

1. Confirm both chains are returned by /supported-chains.
2. Check the required feature flags.
3. Confirm the input and output tokens through /tokens or /search-token.
4. Request a quote to verify live route availability.
5. Display the selected providers and route kind before execution.

See the Supported Chains API for the complete response schema.