Hanzo AIDocs
Sign inAPI key

List options

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

GET /v1/billing/crypto/options

Billing → · All API references → · Get started →

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
200billing.CryptoOptionsok
defaultproblem-detailsrefused

200 body — 2 fields.

FieldInTypeAlwaysDescription
chainsbodystring[]—
tokensbodystring[]—

Failure carries the platform error shape — see Errors.

Examples

hanzo billing crypto options
import { Configuration, BillingApi } from 'hanzoai';

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingCryptoOptions();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import BillingApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = BillingApi(client).get_billing_crypto_options()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.BillingAPI.GetBillingCryptoOptions(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, billing_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = billing_api::get_billing_crypto_options(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BillingApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new BillingApi(client).getBillingCryptoOptions();
curl https://api.hanzo.ai/v1/billing/crypto/options \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches billing through the billing tool, which names its 39 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_billing_accounts"
         }
       }
     }'

Billing API · All Hanzo APIs · Interactive reference

Was this page useful?
PreviousGet depositNextList pdf