Product boundaries
Which 0Bit product owns each public and private workflow.
Use the audience and data owner to choose a product. A URL prefix is a contract, not a cosmetic label.
Public products
| Need | Owner | Surface |
|---|---|---|
| Embed a hosted buy or sell experience | Gate | Gate API plus one web_widget |
| Build directly against Gate sessions, customers, rails, quotes, and webhooks | Gate | https://gate-api.0bit.app |
| Sign in, manage an Organization, complete business verification, or manage keys | 0Bit Institutional | /account/* |
| Consume or provide institutional liquidity | 0Bit Institutional liquidity | /liquidity/* |
| Read sanitized chain and institutional activity | 0Bit Institutional explorer | /explorer/* |
Gate
Gate owns the end-user ramp and hosted widget experience. It runs KYC, payment steps, sessions, customer records, supported-rail discovery, and signed webhook delivery within the Gate product boundary.
Use Gate when the end user enters the 0Bit widget or when a partner integrates directly with Gate's public API. Gate is not a mode of the institutional API, and staff endpoints are not mixed into its partner contract.
0Bit Institutional
0Bit Institutional owns the organization-facing portal and API for Accounts, liquidity, public explorer data, and the separate Institutional RFQ subproduct. A business has one Organization whether it supplies capital, consumes APIs, or does both.
The internal liquid engine supports first-party products but is not a public
integration surface. Partners call /liquidity/*; they never call an engine
port, reserve route, venue connector, or operator endpoint directly.
Legacy DEX and swap routes are retired. Future non-Gate swaps will be supplied by ezero after a separate integration is complete; no compatibility route is available.
Private products and staff surfaces
Operations
All staff authentication, RBAC, review queues, organization administration,
treasury controls, and product operations live under /operations/*. Operations
is not documented as a public API and does not share browser credentials with
partner products.
Pear V4
There is exactly one Pear product, named Pear V4 in the pear_v4
namespace. It owns internal P2P order, customer, chat, case, alert, and fraud
state. Operations reaches it through /operations/pear_v4/*.
Pear's own upstream /api/v1/* routes are a deliberate private service
contract. They are not exposed to partners, not linked from public API
navigation, and not evidence that 0Bit public APIs are versioned.
Identity boundary
Gate and 0Bit Institutional rely on the same Account-issued Organization keys and entitlements. They do not mint competing partner credentials. Read Account model and Organization API keys for the shared identity contract.