# Create run all

URL: https://docs.hanzo.ai/docs/openapi/billing/post-billing-recharge-run-all

> Sweeps every org's auto-recharge and answers what it did.

`POST /v1/billing/recharge/run-all`

> [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/recharge/run-all` |
| **Method**    | `POST`                                             |
| **Operation** | `post_billing_recharge_run-all`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`             |

Sweeps every org's auto-recharge and answers what it did.

PLATFORM AUTHORITY ONLY. It charges saved cards across every tenant, so an org
owner reaching it could sweep-charge the estate; a caller without it is
refused before anything is charged.

The answer explains a sweep that charged nobody as readily as one that
charged: it names how many orgs were considered and how many needed charging,
with a row each.

## Request

The document declares no body for `POST /v1/billing/recharge/run-all`. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's `describe` for `post_billing_recharge_run-all`, which answers from the running route.

## Response

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

`200` body — 10 fields.

| Field                     | In   | Type                 | Always | Description                                                                                                         |
| ------------------------- | ---- | -------------------- | ------ | ------------------------------------------------------------------------------------------------------------------- |
| `charged`                 | body | integer (int64)      | —      | Charged is how many of them were actually charged.                                                                  |
| `orgs`                    | body | integer (int64)      | —      | Orgs is how many orgs the sweep considered — every org with auto-recharge armed, whether or not it needed charging. |
| `results`                 | body | billing.Recharged\[] | —      | Results is one row per org considered, so a sweep that charged nobody is still explainable.                         |
| `results[].amountCents`   | body | integer (int64)      | —      |                                                                                                                     |
| `results[].balanceCents`  | body | integer (int64)      | —      |                                                                                                                     |
| `results[].charged`       | body | boolean              | —      |                                                                                                                     |
| `results[].error`         | body | string               | —      |                                                                                                                     |
| `results[].orgName`       | body | string               | —      |                                                                                                                     |
| `results[].transactionId` | body | string               | —      |                                                                                                                     |
| `results[].userId`        | body | string               | —      |                                                                                                                     |

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

## Examples

**CLI**

```bash
hanzo billing recharge run-all
```

**SDK**

**.ts**

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

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

**.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).post_billing_recharge_run-all()
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.BillingAPI.PostBillingRechargeRun-all(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::post_billing_recharge_run-all(&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).postBillingRechargeRun-all();
```

The method above is the one at the current release of the document. `hanzoai@8.5.914` (npm) and `hanzoai@8.5.914` (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 →](https://docs.hanzo.ai/docs/sdks)

**HTTP**

```bash
curl -X POST https://api.hanzo.ai/v1/billing/recharge/run-all \
  -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)