...
markets returned
public futures API
...
24h notional volume
...
launch-ready examples
liquid, active, low alert
...
markets to review
thin, wide funding, status flags
...
RWA-style markets
...
pre-TGE markets
| Market | Health | Status | 24h volume | Open interest | Funding | Flags | Operating read |
|---|
Operating workflow
- Use launch-ready markets in SDK quickstarts, tutorials, and demo frontends.
- Route thin or high-funding markets into risk review before marketing pushes them.
- Track RWA and pre-TGE markets separately because oracle and liquidity assumptions differ.
- Use reduce-only and inactive states as explicit builder-facing warnings.
Implementation note
GET https://api.orderly.org/v1/public/futures. The console stays read-only. A production builder dashboard would add account-scoped order success, WebSocket health, API errors, deposit status, and Builder ID revenue.
If deployed on Workers, /api/futures proxies the public endpoint to avoid browser CORS surprises.
Decision queues
Recommended default markets
Use these in docs, examples, and builder onboarding because they are active and liquid enough to reduce false negatives during integration.
Review queue
These are markets I would not feature in builder growth material without a specific liquidity, oracle, or status review.