Hanzo
OpenapiBilling

Answers which chains and tokens the crypto rail accepts — what an asset picker…

Answers which chains and tokens the crypto rail accepts — what an asset picker renders.

GET /v1/billing/crypto/options

Addresshttps://api.hanzo.ai/v1/billing/crypto/options
MethodGET
Operationget_billing_crypto_options
AuthAuthorization: Bearer $HANZO_API_KEY

Answers which chains and tokens the crypto rail accepts — what an asset picker renders.

It is the intersection of two live facts rather than a configured list: an asset appears only if something is WATCHING it and the custody processor supports it. An address nobody watches credits nobody, so offering one would take a customer's money and lose it. A rail with nothing armed answers 503, not an empty menu — "no rail" and "no assets" are different, and only one of them means try again later.

A named handler, not a closure, so zipdoc can lift this prose into the registry.

Request

GET /v1/billing/crypto/options takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200CryptoOptionsok

200 body — 2 fields.

FieldInTypeAlwaysDescription
chainsbodystring[]
tokensbodystring[]

Failure carries the platform error shape — see Errors.

Examples

hanzo billing crypto options

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page