Delete methods
Removes one card or account the caller has saved.
DELETE /v1/billing/methods/{id}
| Address | https://api.hanzo.ai/v1/billing/methods/{id} |
| Method | DELETE |
| Operation | delete_billing_methods_by_id |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Removes one card or account the caller has saved.
It detaches only the CALLER'S own — the wallet this request bills from, resolved server-side — so an id belonging to another customer of the same org is not something this operation can reach. A platform or service caller detaches on the subject's behalf, and that authority is decided HERE, where the credential is, and travels as a value: authority decided twice is authority that eventually disagrees with itself.
The card is vaulted at the processor, so what goes is our token for it.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | yes | ID is the saved method to detach, from the path. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | Detachment | ok |
200 body — 2 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
deleted | body | boolean | — | Deleted is whether the method was actually removed. |
id | body | string | — | ID is the method that was detached, echoed so a caller batching several can tell the answers apart. |
Failure carries the platform error shape — see Errors.
Examples
hanzo billing methods rm <id>import { Configuration, BillingApi } from 'hanzoai';
const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteBillingMethodsById({ id: 'id' });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).delete_billing_methods_by_id(id='id')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.BillingAPI.DeleteBillingMethodsById(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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::delete_billing_methods_by_id(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BillingApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new BillingApi(client).deleteBillingMethodsById();curl -X DELETE https://api.hanzo.ai/v1/billing/methods/<id> \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches billing through the billing tool, which names its 9 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": "get_billing_balance"
}
}
}'How is this guide?