Product availability status
Understand which product surfaces are generally available, account-gated, review-only, or internal-boundary.
This page explains how to read product availability in the 0Bit docs. Some surfaces are public developer paths, some require partner entitlement, and some are documented only as review boundaries. Your account configuration and product agreement decide what you can use in production.
Docs are not account enablement
A page in the docs does not automatically enable a product, country, currency, payment method, payout method, pool, or routing path for your account. Check the documented capability endpoints, your account configuration, or support before launch.
Current availability matrix
| Area | Availability status | What you can use from docs | Confirm before production |
|---|---|---|---|
| 0Gate hosted sessions | Public developer path | Server-created sessions, browser-safe embed values, hosted widget/redirect, raw-body webhooks, idempotency, support-safe identifiers | Live account access, supported countries, assets, methods, limits, and support commitments. |
| 0Gate API reference | OpenAPI-backed product reference | Curated public pages backed by the documented 0Gate OpenAPI contract. | Any operation not present in the current reference. |
| Supported countries, assets, methods | Dynamic capability checks | Query capability endpoints or account configuration before showing a flow. | Do not hardcode permanent region, currency, asset, payment-method, payout-method, or eligibility promises. |
| KYC/KYB behavior | Product and account configured | Explain that verification may be required and hosted flows own user-facing verification where applicable. | Exact legal wording, exemptions, regional thresholds, or customer promises. |
| Webhook contract | Product reference backed | Raw-body signature verification, event-id dedupe, at-least-once handling, replay-safe workers. | Event names, fields, retry schedules, and replay behavior for products not covered by your reference. |
| 0Pools | Partner-gated | Entitled pool discovery, quote, execute, trade tracking, and balance availability for approved partners. | Liquidity sources, market-maker terms, treasury behavior, route selection internals. |
| 0Base | Review-only unless enabled | Checkout object and report concepts where your account is enabled. | Live checkout/payment-intent promises, settlement cadence, refund handling, provider details. |
| 0Link | Review/internal-boundary | Routing boundary language and product-positioning guidance. | Internal routing APIs, venue/provider details, best-price claims, execution metrics. |
| 0Pools Scan | Public conceptual/reference docs | Explorer-style records, protocol activity, lookup and reconciliation context. | Treating scan records as legal settlement proof or sole financial truth. |
Launch checklist
Before enabling a production flow, confirm:
- The product surface is enabled for your account and environment.
- Examples use fake keys, fake ids, fake users, fake wallets, and partner-owned domains.
- No server-only key, webhook secret, internal provider name, route algorithm, treasury process, or customer PII appears in the page.
- KYC/KYB, regional availability, asset availability, and method availability are checked dynamically or confirmed for your account.
- Webhook event names and payload fields match the product reference you are using.
- Non-0Gate products are used only when your account is approved for them.
- The support path is
support@0bit.ioand asks for support-safe identifiers only.
Product wording rules
| Claim type | Safe wording | Unsafe wording |
|---|---|---|
| Regions | "Check supported countries before creating a session." | "0Gate supports all EU/US/LatAm countries." |
| KYC/KYB | "The hosted flow may require verification based on the product, region, and partner configuration." | "No KYC is needed" or "KYC is always handled in this exact way." |
| Webhooks | "Verify Gate-Signature against the raw body and dedupe by event id." | "Every event arrives exactly once" or undocumented retry timings. |
| 0Pools | "Approved partners can use entitled pool workflows." | "All developers can access liquidity APIs." |
| 0Base | "Review checkout object boundaries before using 0Base in production." | "0Base is live checkout for every merchant." |
| 0Link | "0Link routing is a review boundary." | "Developers can call internal routing APIs directly." |
Reference sources
| Source | Use |
|---|---|
| OpenAPI-backed API reference | Current documented endpoint shape for product APIs. |
| SDK docs and examples | Package names, imports, base URL shape, session methods, and webhook verifier behavior. |
| Guide pages | Product-safe implementation paths for 0Gate, approved 0Pools, account-enabled 0Base, 0Link boundaries, webhooks, security, and operations. |