0x explained: trading infrastructure behind an interface

0x supplies trading infrastructure that applications can use to offer swaps. A user may encounter its execution through a wallet or trading app without visiting a consumer page called “0x exchange.”

The official documentation organizes its service around APIs and integration products. That matters when comparing it with a retail interface: an API does not itself determine every button, fee label or wallet interaction the end user sees.

There can be more than one commercial layer

The application can add its own service choices on top of the provider. 0x documents integrator monetization, so two products using its infrastructure need not expose identical economic terms.

For a user, identify the frontend, requested approval target and final transaction. For a developer, identify the API product, chain and commercial account. A shared infrastructure label does not prove that two apps use matching settings or versions.

Product support is specific

The support table distinguishes Swap, Gasless and cross-chain coverage. A network appearing anywhere in that table does not make every feature available there. Use the cell corresponding to the product you actually plan to integrate.

What should decide a shortlist?

Begin with the required trading flow: ordinary same-chain transaction, gasless experience or cross-chain movement. Then examine token support, wallet compatibility, fee disclosure and post-trade records. An app that cannot explain a completed order has a product problem even if its preliminary quote was competitive.

Finally, separate marketing reach from execution evidence. A count of integrated sources describes coverage, not a guarantee that a particular pair will have liquidity at your amount. Obtain a valid quote for the actual request and evaluate the resulting transaction, not merely the brand powering it.