Skip to main content
Orderly is an omnichain trading infrastructure that provides orderbook-based trading services and shared liquidity for builders. It lets developers build their own trading application while keeping user settlement on-chain and user custody in the wallet.
Start with the Integration Checklist, then choose the integration path that fits your stack: React Hooks, React UI components, the Python connector, or direct integration through the API docs.
Not everyone does. If you are an API trader using an existing builder, you can select from the available builders through the builder list endpoint. If you are launching your own front end and onboarding your own users, start from Builder Onboarding. If you are using Orderly One, continue from https://dex.orderly.network/.
Builders can configure their own fees on top of Orderly’s base fee model. Builders can define a default fee rate and, if needed, apply custom fee logic for specific users. See Custom Fees for the builder flow and related endpoints.
The builder admin wallet is the wallet associated with your builder setup. It is used for builder-level actions such as fee management and other admin-authenticated endpoints described in the API docs.
Most user data is only accessible by the account holder using the user’s Trading Key. Builders can retrieve builder-scoped data for their own users through dedicated builder endpoints, but not unrestricted data for all users on the system.
Monitor the system maintenance status endpoint and stay in the builder Telegram channel for announcements. Ask the Orderly team for channel access during onboarding. During maintenance, market data and user trading surfaces may be unavailable, so your UI should clearly communicate the maintenance state and only expose order actions that remain available.
Start with Builder Onboarding for builder setup. If you are using Orderly One, continue from https://dex.orderly.network/. For implementation questions, join the Orderly Discord. For a practical overview of support resources, see Partner Support.