Provider documentation can establish what a product is designed to do. It cannot by itself prove that the product gives the best execution for every trader. Read a claim according to the evidence needed to support it.
Classify the claim
| Claim | Useful supporting evidence |
|---|---|
| A chain or order type is supported | Current product reference and a valid eligible quote |
| A fee is a given percentage | Dated fee schedule, conditions and quote breakdown |
| A route uses private execution | Mechanism-specific documentation and transaction path |
| A provider usually gives better prices | Comparable dataset, dates, amounts, costs and exclusions |
For example, the OKX FAQ contains a claim about matching or beating competitors more than 60% of the time. Without the underlying sample and methodology in the retrieved source, this guide treats that as a provider statement, not an independently reproduced result.
Watch the scope of protection
The 0x FAQ distinguishes RFQ execution protection from ordinary AMM routes. Quoting a broad “MEV protected” label without that route boundary can materially change the reader’s expectation.
Likewise, “gasless” describes who submits or funds a transaction, not necessarily a zero economic cost. “Audited” requires a match between the report and the relevant deployed product. A mechanism label should trigger a more specific question, not end the comparison.
What a fair performance record includes
For a price study, retain unsuccessful quote attempts as well as attractive results. Record chain, token contracts, amount, account assumptions, timestamp, execution mode, minimum receipt and separately paid costs. Excluding all unavailable pairs can make a provider look better while concealing a coverage problem.
A one-time quote comparison can support a decision about that offer. It should not be promoted into an enduring ranking. This publication’s provider tables describe documented product differences unless a reproducible performance test is explicitly supplied; they do not imply that transactions were executed or that a universal winner was measured.
Sources & verification (2)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- OKX DEX FAQs
Aggregator interface; dynamic/fixed/capped slippage. General no-platform-fee claim conflicts with dedicated current fee schedule and is not relied upon.
https://web3.okx.com/help/okx-dex-faqs - FAQ
Standard-tier token-dependent zeroExFee; Gasless eligibility and cost treatment; product support conditions.
https://docs.0x.org/docs/introduction/faq