0Bit public documentation

0Bit developer docs

The public integration map for Gate and 0Bit Institutional.

0Bit has two public integration products: Gate and 0Bit Institutional. They share one Account and Organization identity, but each owns an honest API and product boundary.

Product	Use it for	Public surface
Gate	A hosted buy or sell experience through the 0Bit widget, plus Gate sessions, rails, customers, and webhooks	`https://gate-api.0bit.app`
0Bit Institutional	Organization accounts, liquidity, RFQ, and public explorer data	`https://api.0bit.app`

Read Product boundaries if you are deciding which product owns a workflow.

One identity, separate products

A human signs in as one Account and belongs to one or more Organizations. The Organization owns product entitlements and API keys. Gate and 0Bit Institutional verify that same organization authority; neither creates a parallel login or key store.

flowchart LR
    Person[Account member]
    Organization[Organization]
    Keys[Organization API keys]
    Gate[Gate API and web widget]
    Institutional[0Bit Institutional API and portal]

    Person --> Organization
    Organization --> Keys
    Keys --> Gate
    Keys --> Institutional

See Account model and Organization API keys.

Public URL rules

Public product paths are unversioned and have no compatibility-version lane.
0Bit Institutional uses /account, /liquidity, and /explorer.
Gate owns its own unversioned API and one web_widget embed.
Operations and Pear V4 are private surfaces, not partner integrations. See Product boundaries for their exact ownership.

Where to start

Hosted fiat ramp experience: Gate quickstart
Institutional account and API access: 0Bit Institutional
Organization identity: Account model
API credentials: Organization API keys