0Bit public documentation
0Bit Institutional
Account, liquidity, RFQ, and explorer surfaces for institutional organizations.
0Bit Institutional is the product for liquidity providers, market makers,
treasury teams, and API partners. It combines one Account identity with three
honest public URL areas on https://api.0bit.app.
| Prefix | Audience | Purpose |
|---|---|---|
/account/* |
Signed-in organization members | Authentication, organizations, invitations, API keys, entitlements, and verification |
/liquidity/* |
Entitled partner servers, plus explicitly public discovery reads | Quotes, transactions, funding state, reports, webhooks, and the separate RFQ subproduct |
/explorer/* |
Public, read-only callers | Sanitized chain, settlement, corridor, timeseries, and RFQ-market reads |
All three prefixes are unversioned. Retired product-name and role-name compatibility lanes do not exist.
One organization, different capabilities
A business has one Organization even when it both supplies liquidity and consumes APIs. Access differs by entitlements and key scopes, not by creating a second identity or login. Start with the Account model and Organization API keys.
Boundaries that matter
- Gate remains its own public API and hosted widget. Use Gate when 0Bit owns the end-user ramp experience.
- The liquid engine is an internal implementation detail. Partners do not call its port or internal routes directly.
- Staff tools live only under
/operations/*and are not part of this public API. /internal/*is service-to-service traffic and is intentionally absent from the public navigation.- Legacy DEX and swap routes are retired. Future non-Gate swaps will use ezero after a separate integration; no temporary compatibility route exists.
Choose a surface from the sidebar, or use Product boundaries to decide between Gate and 0Bit Institutional.