@leaflow/sdk 0.0.0-dev.35.g30ba751 → 0.0.0-dev.352.g85966ed

package/dist/tunnel/v1/generated/schemas.zod.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+/**
+ * Cut by calendar day. A day carrying no traffic is absent rather than zero, so a chart has to fill the date axis itself.
+ *
+ * These days do not sum to the usage of the current period, which is cut by billing period. Resetting the usage of the current period leaves every daily total in place.
+ * @summary Get daily usage
+ */
+export declare const listL4TunnelUsageSeriesQueryDaysDefault = 30;
+export declare const listL4TunnelUsageSeriesQueryDaysMin = 0;
+export declare const listL4TunnelUsageSeriesQueryDaysMax = 3650;
+export declare const ListL4TunnelUsageSeriesQueryParams: zod.ZodObject<{
+    days: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;

package/dist/tunnel/v1/generated/schemas.zod.js

@@ -0,0 +1,55 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+/**
+ * Cut by calendar day. A day carrying no traffic is absent rather than zero, so a chart has to fill the date axis itself.
+ *
+ * These days do not sum to the usage of the current period, which is cut by billing period. Resetting the usage of the current period leaves every daily total in place.
+ * @summary Get daily usage
+ */
+export const listL4TunnelUsageSeriesQueryDaysDefault = 30;
+export const listL4TunnelUsageSeriesQueryDaysMin = 0;
+export const listL4TunnelUsageSeriesQueryDaysMax = 3650;
+export const ListL4TunnelUsageSeriesQueryParams = zod.strictObject({
+    days: zod
+        .int()
+        .min(listL4TunnelUsageSeriesQueryDaysMin)
+        .max(listL4TunnelUsageSeriesQueryDaysMax)
+        .default(listL4TunnelUsageSeriesQueryDaysDefault)
+        .describe("How many days to cover. 0 requests the default of 30; the range accepted is 1–365, and a larger value is clamped to it"),
+});

package/dist/tunnel/v1/generated/validators/error.zod.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const Error: zod.ZodObject<{
+    code: zod.ZodOptional<zod.ZodString>;
+    message: zod.ZodString;
+    meta: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+    status: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type Error = zod.input<typeof Error>;
+export type ErrorOutput = zod.output<typeof Error>;

package/dist/tunnel/v1/generated/validators/error.zod.js

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const Error = zod.strictObject({
+    code: zod.string().optional(),
+    message: zod.string(),
+    meta: zod
+        .record(zod.string(), zod.unknown())
+        .optional()
+        .describe("What a given `code` carries alongside the message. The keys depend on the code,\nand a client that does not recognise one ignores it."),
+    status: zod.int(),
+});

package/dist/tunnel/v1/generated/validators/listL4TunnelUsageSeriesParams.zod.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const listL4TunnelUsageSeriesParamsDaysDefault = 30;
+export declare const listL4TunnelUsageSeriesParamsDaysMin = 0;
+export declare const listL4TunnelUsageSeriesParamsDaysMax = 3650;
+export declare const ListL4TunnelUsageSeriesParams: zod.ZodObject<{
+    days: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListL4TunnelUsageSeriesParams = zod.input<typeof ListL4TunnelUsageSeriesParams>;
+export type ListL4TunnelUsageSeriesParamsOutput = zod.output<typeof ListL4TunnelUsageSeriesParams>;

package/dist/tunnel/v1/generated/validators/listL4TunnelUsageSeriesParams.zod.js

@@ -0,0 +1,48 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const listL4TunnelUsageSeriesParamsDaysDefault = 30;
+export const listL4TunnelUsageSeriesParamsDaysMin = 0;
+export const listL4TunnelUsageSeriesParamsDaysMax = 3650;
+export const ListL4TunnelUsageSeriesParams = zod.strictObject({
+    days: zod
+        .int()
+        .min(listL4TunnelUsageSeriesParamsDaysMin)
+        .max(listL4TunnelUsageSeriesParamsDaysMax)
+        .default(listL4TunnelUsageSeriesParamsDaysDefault),
+});

package/dist/tunnel/v1/generated/validators/subscriptionResource.zod.d.ts

@@ -0,0 +1,49 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const SubscriptionResource: zod.ZodObject<{
+    status: zod.ZodEnum<{
+        preparing: "preparing";
+        ready: "ready";
+    }>;
+    updated_at: zod.z.ZodISODateTime;
+    url: zod.ZodString;
+    version: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type SubscriptionResource = zod.input<typeof SubscriptionResource>;
+export type SubscriptionResourceOutput = zod.output<typeof SubscriptionResource>;

package/dist/tunnel/v1/generated/validators/subscriptionResource.zod.js

@@ -0,0 +1,48 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const SubscriptionResource = zod.strictObject({
+    status: zod
+        .enum(["preparing", "ready"])
+        .describe("ready means every node has been distributed; preparing means distribution is still under way, and the link works either way"),
+    updated_at: zod.iso.datetime({ offset: true }),
+    url: zod
+        .string()
+        .describe("The subscription address. It is a long-lived credential equivalent to a password; do not forward it or share a screenshot of it"),
+    version: zod.int(),
+});

package/dist/tunnel/v1/generated/validators/tunnelResource.zod.d.ts

@@ -0,0 +1,45 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const TunnelResource: zod.ZodObject<{
+    created_at: zod.z.ZodISODateTime;
+    enabled: zod.ZodBoolean;
+    id: zod.ZodUUID;
+}, zod.z.core.$strict>;
+export type TunnelResource = zod.input<typeof TunnelResource>;
+export type TunnelResourceOutput = zod.output<typeof TunnelResource>;

package/dist/tunnel/v1/generated/validators/tunnelResource.zod.js

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const TunnelResource = zod
+    .strictObject({
+    created_at: zod.iso.datetime({ offset: true }),
+    enabled: zod
+        .boolean()
+        .describe("Whether the tunnel is currently usable. false means the platform has disabled it — for an unpaid balance, a violation, or a suspended project — and the cause has to be resolved first"),
+    id: zod.uuid(),
+})
+    .describe("The layer 4 tunnel of the current project. It answers a single question — whether the tunnel has been generated");

package/dist/tunnel/v1/generated/validators/usageDayResource.zod.d.ts

@@ -0,0 +1,45 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const UsageDayResource: zod.ZodObject<{
+    billed_bytes: zod.ZodInt;
+    day: zod.ZodString;
+    raw_bytes: zod.ZodInt;
+}, zod.z.core.$strict>;
+export type UsageDayResource = zod.input<typeof UsageDayResource>;
+export type UsageDayResourceOutput = zod.output<typeof UsageDayResource>;

package/dist/tunnel/v1/generated/validators/usageDayResource.zod.js

@@ -0,0 +1,43 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const UsageDayResource = zod.strictObject({
+    billed_bytes: zod.int(),
+    day: zod.string().describe("YYYY-MM-DD"),
+    raw_bytes: zod.int(),
+});

package/dist/tunnel/v1/generated/validators/usageResource.zod.d.ts

@@ -0,0 +1,51 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Tunnel API
+ * The user-facing API of Leaflow Tunnel: generating a tunnel for a project, reading its subscription address, and reading its traffic usage.
+ *
+ * ## Layer 4 only
+ *
+ * The platform offers tunnels at layers 2, 3 and 4. **Every endpoint in this document belongs to layer 4** and is served under `/tunnel/l4`. Layers 2 and 3 are not yet open and will carry their own prefixes.
+ *
+ * ## Layer 4 is entitled per project, and no project holds it by default
+ *
+ * **Every endpoint in this document requires the current project to have been entitled.** Without the entitlement each one answers 403 `TUNNEL_NOT_ENTITLED`. Entitlement is granted by the platform per project and cannot be obtained by the user.
+ *
+ * `TUNNEL_NOT_ENTITLED` and `TUNNEL_NOT_FOUND` state different things and cannot be handled as one. The first means the project has not been entitled; the second means it has, and no tunnel has been generated yet.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Conventions
+ *
+ * - **One layer 4 tunnel per project.** The path is therefore the singular `/tunnel/l4` and carries no id.
+ *
+ * - **Generation is idempotent.** Calling it again returns the existing tunnel rather than an error.
+ *
+ * - **The subscription address is a credential.** It is equivalent to a password, is returned only by `GET /tunnel/l4/subscription`, and appears neither in the tunnel itself nor in any list. Do not call that endpoint before the user asks for the address. Rotate it whenever it may have been exposed; every subscription already distributed stops working at once.
+ *
+ * - **`preparing` does not mean unusable.** The subscription link works while nodes are still being distributed, and its contents are derived at the moment it is fetched.
+ *
+ * - **Only `billed_bytes` decides whether the quota is exceeded.** A route may carry a multiplier such as 1.5× or 0×, so `raw_bytes`, the volume actually transferred, need not equal it. A `quota_bytes` of 0 means unlimited.
+ *
+ * - **Usage lags by up to one collection interval.** It suits usage control rather than settlement.
+ *
+ * - **Daily usage does not sum to the usage of the current period.** One is cut by calendar day and the other by billing period.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const UsageResource: zod.ZodObject<{
+    billed_bytes: zod.ZodInt;
+    over_quota: zod.ZodBoolean;
+    period_end: zod.ZodString;
+    period_start: zod.ZodString;
+    quota_bytes: zod.ZodInt;
+    quota_exceeded_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    raw_bytes: zod.ZodInt;
+    upload_bytes: zod.ZodInt;
+    usage_percent: zod.ZodNumber;
+}, zod.z.core.$strict>;
+export type UsageResource = zod.input<typeof UsageResource>;
+export type UsageResourceOutput = zod.output<typeof UsageResource>;