@hunt-labs/bytekit-sdk 0.7.1 → 0.7.3

package/CHANGELOG.md

@@ -10,6 +10,32 @@ today, see [README.md](./README.md), which remains the authoritative usage guide
 
 ## [Unreleased]
 
+## [0.7.3] - 2026-08-18
+
+### Changed
+
+- **`XFetchContentLength`'s description no longer calls the header a wire-byte count** (#3133).
+  `X-Fetch-Content-Length` is the byte length of the response body actually served: on a
+  passthrough `/v1/fetch` (no `format`) that is the relayed upstream payload, so it does equal
+  the upstream wire bytes — but with `format=html` or `format=markdown` the gateway overwrites
+  it with the transformed document's length, which is typically far smaller than what is billed.
+  The old description therefore read as a billing discrepancy on every transform request. Billing
+  is unchanged and has always used the upstream compressed wire bytes reported by `X-Raw-Bytes` /
+  `X-Billable-Bytes`. Generated-type comments only; no type or runtime behavior changes.
+
+## [0.7.2] - 2026-08-17
+
+### Changed
+
+- **`ScrapeResponses.202`'s headers no longer advertise `X-Raw-Bytes`, `X-Billable-Bytes`, or
+  `X-Billing-Multiplier`** (#3068). The gateway's async `/v1/scrape` path only ever emitted
+  `X-Scrape-ID` and `X-Scrape-Status: queued` on a 202 — a queued scrape has no finalized byte
+  charge yet — but `docs/api/openapi.yaml` documented the billing-transparency trio there too,
+  so `src/generated/api.d.ts` typed three response headers the runtime never sends. This corrects
+  the generated type to match the gateway's actual behavior; it does not change any runtime
+  behavior. The synchronous `200` response, and `/v1/screenshots`' `202` (which does finalize a
+  charge before responding), are unaffected.
+
 ## [0.7.1] - 2026-08-11
 
 ### Changed
@@ -508,6 +534,8 @@ against 0.1.0 — read each one before upgrading.
   `@rapidcrawl/sdk` name.
 
 [Unreleased]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
+[0.7.3]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
+[0.7.2]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
 [0.7.1]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
 [0.7.0]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript
 [0.6.2]: https://github.com/Hunt-Labs-Inc/ByteKit/tree/main/packages/sdk-typescript

package/dist/generated/api.d.ts

@@ -2626,7 +2626,14 @@ export interface components {
          */
         XFetchStatus: "completed";
         XFetchURL: string;
-        /** @description Wire byte count (integer as string). */
+        /**
+         * @description Byte length of the response body served on this request (integer as string) — NOT the
+         *     billing basis. On a passthrough request (no `format`) the body is the relayed upstream
+         *     payload, so this equals the upstream wire byte count. With `format=html` or
+         *     `format=markdown` the body is the transformed document, so this is the transformed byte
+         *     count and is typically far smaller than what is billed. Billing always reads the upstream
+         *     compressed wire bytes from `X-Raw-Bytes` / `X-Billable-Bytes`, on every path.
+         */
         XFetchContentLength: string;
         XFetchCreditsCharged: string;
         XFetchDurationMs: string;
@@ -3372,12 +3379,6 @@ export interface operations {
                     "X-Scrape-ID"?: string;
                     /** @description Always `queued` on a 202 response. */
                     "X-Scrape-Status"?: "queued";
-                    /** @description Upstream wire bytes (0 when not yet fetched on async paths). */
-                    "X-Raw-Bytes"?: number;
-                    /** @description Chargeable bytes after applying the billing multiplier. */
-                    "X-Billable-Bytes"?: number;
-                    /** @description Bandwidth cost multiplier applied to X-Raw-Bytes. A markdown fetch bills as fetch_md (miss 1.5, hit 0.75); a raw fetch bills 1.0 on a miss, 0.5 on a cache hit. */
-                    "X-Billing-Multiplier"?: number;
                     [name: string]: unknown;
                 };
                 content: {

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.7.1";
+export declare const SDK_VERSION = "0.7.3";

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.7.1';
+export const SDK_VERSION = '0.7.3';

package/package.json

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