Support matrix
Understand which 0Bit product surfaces, environments, assets, credentials, and event contracts are public-candidate, review-only, partner-gated, or internal-only.
The support matrix is a documentation boundary, not a commercial availability promise. Use it to choose the right product path and to avoid treating example assets, example routes, or generated API surfaces as live support for every partner.
Confirm live access before launch
Before you show a workflow as live, confirm product entitlement, environment, region, asset/currency support, payment method, payout method, rail status, and compliance approval with 0Bit.
Product status
| Area | Public docs status | Build against it when | Do not assume |
|---|---|---|---|
| 0Gate | Candidate public developer path. | You are building hosted buy, sell, swap, or payment-session flows. | Every country, asset, payment method, payout method, or rail is enabled. |
| Gate SDK | Candidate public developer path pending package/version review. | You use server helpers, browser embed helpers, React helpers, or webhook verification utilities. | Package versions or method surfaces are final without release confirmation. |
| 0Pools | Partner-gated and liquidity-sensitive. | You are an approved headless liquidity partner with your own UX and compliance flow. | Public, self-serve, provider-level, treasury-level, or routing-level access. |
| 0Base | Foundation/review-only. | Product and Engineering approve the object, report, settlement, and provider behavior for your environment. | Live checkout, refunds, settlement, payouts, or money movement. |
| 0Link | Product docs only, public endpoint contract not assumed. | Product approves connected app/link workflows for your use case. | Internal routing, large-order execution, provider terms, or desk workflows. |
| 0Pools Scan | Public-safe explorer-style docs. | You need read visibility into transactions, swaps, assets, mint/burn events, pool activity, and statuses. | A webhook contract, legal attestation, or internal indexer API. |
| Partner Hub | Partner-confidential account/admin UI. | You are an approved partner admin using managed UI access. | A public API package or self-serve onboarding contract. |
| Internal services | Not public. | Never from public docs. | Direct partner access to internal operations, provider, treasury, reserve, or settlement systems. |
Environment matrix
| Product | Environment | Base URL | Public-safe interpretation |
|---|---|---|---|
| 0Gate | Sandbox | https://gate-api-sandbox.0bit.app/v1 | Candidate public test integration path. |
| 0Gate | Production | https://gate-api.0bit.app/v1 | Requires live keys, entitlement, and launch approval. |
| 0Gate | Local dev | http://localhost:4000/v1 | Local development reference. |
| 0Base | Sandbox | https://base-api-sandbox.0bit.app/v1 | Review-only foundation/testing reference. |
| 0Base | Production | https://base-gate-api.0bit.app/v1 | Do not treat as live launch evidence without approval. |
| 0Base | Local dev | http://localhost:4600/v1 | Local development reference. |
| 0Pools | Production | https://pools-api.0bit.app/v1 | Approved partner-only headless liquidity API. |
| 0Pools | Local dev | http://localhost:4100/v1 | Local/reference only, not public availability. |
Credential matrix
| Credential | Safe location | Product use |
|---|---|---|
pk_test_* / pk_live_* publishable key | Browser/mobile only where explicitly allowed. | 0Gate embed bootstrap and approved discovery-style calls. |
sk_test_* / sk_live_* secret key | Partner server only. | Create sessions, lock quotes, execute writes, read protected records. |
| Product client secret | Browser only for one server-created object. | Bind a hosted 0Gate experience to a session. |
whsec_* webhook secret | Partner server only. | Verify inbound webhook signatures. |
| Idempotency key | Partner server-generated and stored with a logical write. | Deduplicate retries for sessions, quotes, transactions, payment objects, and refunds. |
Asset and currency examples
The docs use configured 0Asset examples to explain asset-aware workflows:
| Asset | Example use in docs | Availability boundary |
|---|---|---|
| 0EUR | EUR-denominated payment, settlement, and swap examples. | Example/configured asset, not universal live support. |
| 0BRL | BRL liquidity and asset activity examples. | Region, rail, entitlement, and compliance dependent. |
| 0NGN | NGN receive and pool route examples. | Region, rail, entitlement, and compliance dependent. |
| 0COP | Mint/burn and scan activity examples. | Lifecycle visibility does not equal legal reserve attestation. |
| 0MXN | Burn/redeem-style lifecycle examples. | Settlement timing and redemption behavior require approval. |
| USDT | Common quote, settlement, or swap counterpart in examples. | Route support varies by product, network, partner, and environment. |
Use capability endpoints and product approval for live support. Do not infer production availability from an example page.
Event and webhook matrix
| Product | Event contract | Public-safe use |
|---|---|---|
| 0Gate | Source-backed signed events and delivery operations. | Verify, dedupe, persist, and reconcile session/customer/quota/test events. |
| 0Gate restricted rails | Entitlement-gated event names exist in source. | Use only if the rail flow is enabled for your account. |
| 0Base | Foundation/review-only delivery evidence. | Treat as reporting/object-model documentation until approved. |
| 0Pools | Partner-gated and liquidity-sensitive evidence. | Use only approved quote/trade status handling for entitled partners. |
| 0Pools Scan | Read visibility pages. | Use API reads or explorer pages for status, not webhook fulfillment. |
What to verify before launch
| Topic | Verify |
|---|---|
| Product | Which product owns the workflow and whether the product is enabled for the partner. |
| Environment | Sandbox versus live host, key prefix, webhook secret, and callback/origin configuration. |
| Geography | Supported country, region, corridor, and compliance restrictions. |
| Assets | Asset symbols, networks, routes, liquidity, and settlement or scan visibility. |
| Payments | Payment methods, payout methods, hosted flow status, settlement expectations, and refund behavior. |
| Webhooks | Event types, signature header, endpoint URL, retry behavior, dead-letter replay process, and duplicate handling. |
| Operations | Request ids, event ids, object ids, reporting fields, reconciliation ownership, and support escalation path. |