@hunt-labs/bytekit-sdk 0.11.6 → 0.11.7

package/CHANGELOG.md

@@ -10,6 +10,15 @@ today, see [README.md](./README.md), which remains the authoritative usage guide
 
 ## [Unreleased]
 
+## [0.11.7] - 2026-09-29
+
+### Changed
+
+- **Internal `GET /v1/billing/topup-balance` types add `bandwidth.debt_bytes` (#4960, #4975).**
+  The bytes the account still owes for bandwidth a finished request used beyond everything it
+  could pay for, net of any repaid. Declared on that endpoint only, not on the shared
+  `BandwidthBalance` schema `GET /v1/usage` returns. No SDK method calls it.
+
 ## [0.11.6] - 2026-09-24
 
 ### Changed

package/dist/generated/api.d.ts

@@ -2838,10 +2838,13 @@ export interface components {
          *     performed. The unified `Error` envelope carries one of the billing codes
          *     below in `error.code`; match on the code, never on the prose.
          *
-         *     - `quota_exceeded` — the enforced balance for this request's meter is
-         *       exhausted. Capture endpoints (`/v1/scrape`, `/v1/fetch`,
+         *     - `quota_exceeded` — the enforced balance for this request's meter
+         *       cannot fund it. Capture endpoints (`/v1/scrape`, `/v1/fetch`,
          *       `/v1/screenshots`, `/v1/sitemap` and the bulk siblings) meter
-         *       bandwidth; `/v1/search` meters credits.
+         *       bandwidth: they reject when the balance cannot fund the request's
+         *       byte reservation, and `error.details.required_bytes` and
+         *       `error.details.available_bytes` report the bytes the request reserves
+         *       and the bytes available. `/v1/search` meters credits.
          *     - `spending_cap_reached` — the request would push overage spend past the
          *       account's configured cap. Only reachable on a custom overage-enabled
          *       plan; standard plans stop at `quota_exceeded`.
@@ -2864,9 +2867,13 @@ export interface components {
                  *       "status": "failed",
                  *       "error": {
                  *         "code": "quota_exceeded",
-                 *         "message": "Monthly bandwidth quota exhausted.",
+                 *         "message": "Insufficient bandwidth balance: this request reserves 102400 bytes and 4321 are available.",
                  *         "http_status": 402,
-                 *         "failed_at": "2026-01-15T12:00:00Z"
+                 *         "failed_at": "2026-01-15T12:00:00Z",
+                 *         "details": {
+                 *           "required_bytes": 102400,
+                 *           "available_bytes": 4321
+                 *         }
                  *       }
                  *     }
                  */
@@ -6597,6 +6604,8 @@ export interface operations {
                         bandwidth: components["schemas"]["BandwidthBalance"] & {
                             /** @description Remaining balance of your subscription allowance: bytes still unspent across all allowance lots, the current period's and any rolled over from earlier periods alike, after active refund reservations. This is a remaining balance and falls to zero as the allowance is drawn down. It is not `included_bytes`, which is the plan's configured grant for a period and does not move as it is spent; do not subtract one from the other. `rollover_bytes` is a subset of this figure. */
                             remaining_allowance_bytes: number;
+                            /** @description Bytes you still owe: bandwidth your finished requests used beyond everything your account could pay for, net of any already paid back. It is reported beside the other bandwidth figures and is not subtracted from `remaining_bytes` or `remaining_allowance_bytes`. 0 when nothing is owed. */
+                            debt_bytes: number;
                         };
                         credits: components["schemas"]["CreditBalance"];
                         rates: {

package/dist/version.d.ts

@@ -5,4 +5,4 @@
  * outbound request carries — see the emit site in `client.ts`. The header name is spelled
  * only there, so issue #2905's pre-merge gate 1 counts exactly one occurrence in `src/`.
  */
-export declare const SDK_VERSION = "0.11.6";
+export declare const SDK_VERSION = "0.11.7";

package/dist/version.js

@@ -9,4 +9,4 @@
  * outbound request carries — see the emit site in `client.ts`. The header name is spelled
  * only there, so issue #2905's pre-merge gate 1 counts exactly one occurrence in `src/`.
  */
-export const SDK_VERSION = '0.11.6';
+export const SDK_VERSION = '0.11.7';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hunt-labs/bytekit-sdk",
-  "version": "0.11.6",
+  "version": "0.11.7",
   "description": "Official TypeScript SDK for the ByteKit API",
   "license": "MIT",
   "type": "module",