Reading the 0x chain-support matrix correctly

A 0x-supported network is not necessarily supported by every 0x product. Read the official matrix as a set of product-specific claims, checked for this guide on September 24, 2026.

Same-chain support has separate columns

The documentation gives Swap and Gasless their own columns. BNB Smart Chain appears under both at the checked date, while some other rows differ between the products. Copying the complete Swap list into a Gasless selector would therefore overstate coverage.

This distinction also helps users evaluate a wallet's message. “Unsupported network” might mean unsupported by the selected execution mode, not unsupported by the entire provider.

Cross-chain coverage adds direction and provider

The cross-chain table is organized by network and bridge provider, with origin-only or destination-only exceptions where applicable. Thus a supported chain pair still needs an eligible provider route, direction and asset combination.

For a product requirements document, record source chain, destination chain, API product, required asset and intended recipient type. A single checkbox called “multi-chain” cannot express those constraints.

Support is necessary, not sufficient

Even a supported product/network combination does not guarantee a quote for every token and amount. Liquidity, token behavior and service restrictions remain separate checks. Do not direct a user to fund a new network solely because its name appears in a marketing banner.

Maintain the evidence

Keep a dated copy of the relevant product rows in your integration notes and recheck before exposing a new route. If a UI caches a list indefinitely, it can continue advertising a removed feature or hide a newly available one.

For an individual trade, verify the current quote and confirmation details. For an app launch, test the exact product flow promised to users. Neither task is completed merely by counting how many chain logos a provider displays.