# List options

URL: https://docs.hanzo.ai/docs/openapi/billing/get-billing-crypto-options

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

`GET /v1/billing/crypto/options`

> [Billing →](https://docs.hanzo.ai/docs/openapi/billing) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                                  |
| ------------- | ------------------------------------------------ |
| **Address**   | `https://api.hanzo.ai/v1/billing/crypto/options` |
| **Method**    | `GET`                                            |
| **Operation** | `get_billing_crypto_options`                     |
| **Auth**      | `Authorization: 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

| Status    | Body                  | Meaning |
| --------- | --------------------- | ------- |
| `200`     | billing.CryptoOptions | ok      |
| `default` | problem-details       | refused |

`200` body — 2 fields.

| Field    | In   | Type      | Always | Description |
| -------- | ---- | --------- | ------ | ----------- |
| `chains` | body | string\[] | —      |             |
| `tokens` | body | string\[] | —      |             |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo billing crypto options
```

**SDK**

**.ts**

```ts
import { Configuration, BillingApi } from 'hanzoai';

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingCryptoOptions();
```

**.py**

```python
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()
```

**.go**

```go
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
}
```

**.rs**

```rust
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?;
```

**.java**

```java
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();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/billing/crypto/options \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

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:

```bash
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](https://docs.hanzo.ai/docs/openapi/billing) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)