List gateway

Answers the terms to sign a USDC top-up against, for an agent or a person paying from a wallet: the treasury to pay, the networks and USDC contracts, the EIP-712 domain and types, the limits, and a nonce issued to the caller.

GET /v1/billing/crypto/gateway

Addresshttps://api.hanzo.ai/v1/billing/crypto/gateway
MethodGET
Operationget_billing_crypto_gateway
AuthAuthorization: Bearer $HANZO_API_KEY

Answers the terms to sign a USDC top-up against, for an agent or a person paying from a wallet: the treasury to pay, the networks and USDC contracts, the EIP-712 domain and types, the limits, and a nonce issued to the caller.

Sign TransferWithAuthorization {from, to: payTo, value, validAfter, validBefore, nonce} under one network's domain, then POST it here with the salt. The nonce is the caller's own: a payment signed against it credits the caller and cannot be presented by anyone else.

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

Request

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

Response

StatusBodyMeaning
200billing.GatewayTermsok
defaultproblem-detailsrefused

200 body — 23 fields.

FieldInTypeAlwaysDescription
acceptsbodybilling.GatewayAccept[]—
accepts[].assetbodystring—
accepts[].decimalsbodyinteger (int64)—
accepts[].domainbodybilling.GatewayDomain—
accepts[].domain.chainIdbodyinteger (int64)—
accepts[].domain.namebodystring—
accepts[].domain.verifyingContractbodystring—
accepts[].domain.versionbodystring—
accepts[].maxAmountbodystring—
accepts[].minAmountbodystring—
accepts[].minValiditySecondsbodyinteger (int64)—
accepts[].networkbodystring—
accepts[].symbolbodystring—
maxCentsbodyinteger (int64)—
maxValiditySecondsbodyinteger (int64)—
minCentsbodyinteger (int64)—
noncebodystring—
payTobodystring—
primaryTypebodystring—
saltbodystring—
schemebodystring—
typesbodyany—
x402Versionbodyinteger (int64)—

Failure carries the platform error shape — see Errors.

Examples

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

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingCryptoGateway();
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_gateway()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.BillingAPI.GetBillingCryptoGateway(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_gateway(&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).getBillingCryptoGateway();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

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

Tool billing, op get_billing_crypto_gateway — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.

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

Billing API · All Hanzo APIs · Interactive reference

Was this page useful?
Broken link or missing step? Drop it in #docs on Discord or open a PR.