Assets API
Read asset capabilities, validate target tokens, and connect 0Asset activity to sessions, pools, scan records, mint/burn events, and settlement views.
The Assets API page explains how integrations should use asset capability information and asset-related records. It is not a live reserve attestation, a legal support matrix, or a guarantee that every 0Asset is available in every environment.
0Gate exposes public-candidate capability reads for supported crypto assets. The broader docs also use 0Assets such as 0EUR, 0BRL, 0NGN, 0COP, and 0MXN to explain swaps, mint/burn records, pool activity, settlement-aware records, and 0Pools Scan views.
What this page covers
- Reading supported asset capability data.
- Validating target assets before session or quote creation.
- Mapping asset symbols into 0Gate, 0Pools, 0Base, 0Link, and 0Pools Scan.
- Avoiding unsupported availability, reserve, or legal claims.
- Logging asset, network, request, and event identifiers for reconciliation.
Asset capability endpoints
| Method | Path | Purpose | Auth |
|---|---|---|---|
GET | /capabilities/assets | List supported crypto assets for the current configuration. | Secret key from your server. |
GET | /capabilities/assets/{symbol} | Retrieve one asset by symbol, such as USDT. | Secret key from your server. |
curl -X GET https://gate-api-sandbox.0bit.app/v1/capabilities/assets \
-H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Capability reads are planning inputs. Use them to decide what to show or validate, then create the actual session, quote, payment, or scan query through the product-specific flow.
Asset model
| Concept | Meaning | Example |
|---|---|---|
| Asset symbol | The asset identifier shown in product docs. | USDT, 0EUR, 0BRL, 0NGN, 0COP, 0MXN. |
| Network | The supported network or rail context where relevant. | arbitrum, or another configured network value. |
| Fiat reference | The fiat currency an 0Asset example references. | 0EUR references EUR. |
| Capability record | Product/environment view of what can be selected. | Asset appears in a capability response. |
| Activity record | Event or transaction showing asset movement. | Swap, mint, burn, pool transaction, settlement record. |
Product use
| Product | How assets appear |
|---|---|
| 0Gate | Target tokens and asset support can constrain hosted buy/sell/swap sessions. |
| 0Pools | Asset pairs, quote assets, networks, fee fields, trade status, and pool activity. |
| 0Base | Payment objects, ledgers, reports, accounts, and transaction records can carry asset context. |
| 0Link | Links may carry asset-related payment, invoice, account, asset, swap, or transaction references without exposing internal routing. |
| 0Pools Scan | Explorer-style views show transaction, swap, mint/burn, and asset activity records. |
Validation pattern
- Read current capability data for the environment.
- Check the asset symbol, network, amount, side, and product entitlement.
- Create the session, quote, payment object, or link from the server.
- Store asset symbol, network, object id, request id, and your partner reference.
- Reconcile the final status through signed webhooks, trusted API reads, scan records, or settlement reports.
Public documentation boundary
Public asset docs may explain:
- Asset symbols used in examples.
- Capability reads and validation.
- Product-specific places where asset fields appear.
- Mint/burn and settlement lifecycle concepts at a high level.
- Scan visibility for asset activity.
Public asset docs must not claim:
- Legal reserve status.
- Guaranteed redemption timing.
- Universal regional availability.
- Provider or treasury details.
- Private bank rails.
- Contractual support for every asset/corridor.