0Gate capabilities
Read supported countries, currencies, assets, payment methods, payout methods, and eligibility before creating a hosted 0Gate session.
0Gate capability endpoints are read-only planning tools. Use them to decide which countries, currencies, assets, payment methods, payout methods, or regions should be shown to a user before you create a session.
Capabilities are not a public guarantee that every option is live for every partner. Availability can vary by environment, entitlement, region, compliance review, product status, and operating mode.
Endpoints
| Method | Path | Operation id | Purpose |
|---|---|---|---|
GET | /capabilities/countries | listCountries | Supported countries. |
GET | /capabilities/currencies | listCurrencies | Supported fiat currencies. |
GET | /capabilities/assets | listAssets | Supported crypto assets. |
GET | /capabilities/assets/{symbol} | getAsset | Retrieve one asset, such as USDT. |
GET | /capabilities/payment-methods | listPaymentMethods | Buy-side payment methods. |
GET | /capabilities/payout-methods | listPayoutMethods | Sell-side payout methods. |
GET | /capabilities/eligibility | checkEligibility | Region and optional currency/asset eligibility probe. |
Eligibility probe
Eligibility answers whether a user in a region can use the ramp, optionally for a given currency or asset. It does not create a session, lock a quote, or move money.
curl -X GET "https://gate-api-sandbox.0bit.app/v1/capabilities/eligibility?country_code=GB¤cy=EUR&asset=USDT" \
-H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"The source describes an unsupported or unresolved region returning eligible: false with a machine-readable unavailable_reason. Use that response to disable the flow clearly rather than sending the user into a session that will fail later.
Capability use pattern
Implementation rules
| Rule | Reason |
|---|---|
| Read capabilities at runtime or cache briefly. | Static support matrices drift. |
| Keep server credentials server-side. | Capability reads may require secret-key auth. |
| Validate target asset/network before session creation. | Prevents bad session requests. |
| Do not publish provider or bank-rail internals. | Capability docs are not operational runbooks. |
| Branch on machine-readable unavailable reasons. | Avoid brittle string parsing. |
Asset example
curl -X GET https://gate-api-sandbox.0bit.app/v1/capabilities/assets/USDT \
-H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Use GET /capabilities/assets/{symbol} when a user or app already selected a symbol and you need to confirm it is currently supported for the environment.
Public boundary
These pages can explain how to query capability data and how to treat it. They should not hard-code legal support claims, contractual coverage, provider names, reserve status, or live availability for every country, asset, or payment method.