Build with Omega
Developer documentation for a verifiable omnichain exchange. Start with market data, integrate market and limit orders, then reconcile what happened.
From first request
to a result you
can verify.
Market data. Bounded orders. Clear reconciliation.
Start building →Browse API reference ↗/market/exchange-info↗/trade/order↗/trade/account/trades↗Target routes under /v1 · schematic only
A clear path from request to result#
An accepted request is not a fill. A fill is not final settlement. The integration path keeps each observation visible, with stable identifiers for recovery.
Choose where to start#
Start building
Walk from account access to an order you can reconcile.
02Explore the API
Find a resource, its examples and its recovery path.
03Understand the model
Learn what is private, verifiable and final.
The exchange model, briefly#
Omega's current scope is a lit order book with private balances, market and limit orders, and indicative just-in-time quotes. Payments and FX integrations use the exchange as a secondary use case.
A TEE supports execution verification. It does not hide transactions from Omega's operator. MVP data availability relies on server-hosted data. Read the architecture and trust model before making assumptions about confidentiality or recovery.
About this specification#
These docs describe the intended API and preserve synthetic request/response examples. A hosted base URL and production signing contract are not yet supplied. Specific unresolved details appear beside the affected endpoint or guide.