Deprecation and Link response headers. The earlier combined claim-write route is retired; use the fee-claim route below.
Product and funding compatibility
Existing requests keep the non-tax default. For Base, Robinhood, BSC, Monad, X Layer or Arc Tax configuration or creation, explicitly sendlaunch_product=tax (query) or launch_product: "tax" (JSON). market=standard still means crypto-paired, not non-tax. Use the returned suite’s token mode and tax_format; all six Tax deployments are ERC-20 and use inclusive, while Base Standard remains B20.
Do not reinterpret old BPS fields as the new six-decimal percentage units. Use the current Tax launch object, keep historical ABI decoding, and resolve existing tokens by their recorded factory. Select the matching chain and suite from the Tax deployment table, as exposed by the deployed API, with dividend_accounting: "fee-accrual". Use Claim for already-assigned rewards. Earlier Tax identities remain for indexing and direct recovery, not public transaction preparation. Fee-claim requests retain their original meaning.
$O launches use launch_product: "wsto" on Base or Robinhood. This does not change omitted product selection, which remains Standard. Optional dev_buy supports native or admitted paired-token funding. For compatibility, omitted dev_buy.funding_token means native currency on Standard/Tax and held wstO on $O launches. Specify the address explicitly for new clients and use its decimals for amount_in_raw.
Optional settlement_token on swap quotes selects the payment/receipt asset. Omitting it still means the launch pool’s paired asset. Read the per-quote configuration for supported alternatives; do not reinterpret old input amounts in a newly selected currency. Approval continuations and final simulation are described in launch preparation.
Route replacements
Token browsing now uses self-contained sort values:
newest, oldest, trending, liquidity, market_cap, or volume_24h. Do not send a separate order parameter.
Metadata-document preparation removes the operation field. Send actor and document directly and continue supplying Idempotency-Key.
No sunset date is currently announced. Integrations should migrate to the focused routes so unsupported parameter combinations cannot be constructed.