@leaflow/sdk 0.0.0-dev.389.g87f5860 → 0.0.0-dev.391.g0aed14e

package/dist/canopy/v1/generated/validators/listApiKeysParams.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/listRequestsParams.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/listRequestsParams.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/listUsageByApiKeyParams.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/listUsageByApiKeyParams.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/listUsageByModelParams.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/listUsageByModelParams.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modality.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modality.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/model.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/model.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/{modelPricing.zod.d.ts → modelBilling.zod.d.ts}

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,13 +35,13 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-export declare const ModelPricing: zod.ZodObject<{
-    currency: zod.ZodString;
-    token_kinds: zod.ZodArray<zod.ZodObject<{
+export declare const ModelBilling: zod.ZodObject<{
+    plan_id: zod.ZodNullable<zod.ZodUUID>;
+    meters: zod.ZodArray<zod.ZodObject<{
         token_kind: zod.ZodEnum<{
             output: "output";
             input: "input";
@@ -49,9 +49,9 @@ export declare const ModelPricing: zod.ZodObject<{
             cache_read: "cache_read";
             cache_write: "cache_write";
         }>;
-        unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-        unit_quantity: zod.ZodNullable<zod.ZodString>;
+        meter_lookup_key: zod.ZodString;
+        dimensions: zod.ZodRecord<zod.ZodString, zod.ZodString>;
     }, zod.z.core.$strict>>;
 }, zod.z.core.$strict>;
-export type ModelPricing = zod.input<typeof ModelPricing>;
-export type ModelPricingOutput = zod.output<typeof ModelPricing>;
+export type ModelBilling = zod.input<typeof ModelBilling>;
+export type ModelBillingOutput = zod.output<typeof ModelBilling>;

package/dist/canopy/v1/generated/validators/{modelPricing.zod.js → modelBilling.zod.js}

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,16 +35,19 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-import { TokenPrice } from "./tokenPrice.zod.js";
-export const ModelPricing = zod
+import { ModelMeter } from "./modelMeter.zod.js";
+export const ModelBilling = zod
     .strictObject({
-    currency: zod.string(),
-    token_kinds: zod
-        .array(TokenPrice)
+    plan_id: zod
+        .uuid()
+        .nullable()
+        .describe("The Billing plan of the service; null where the service is not sold."),
+    meters: zod
+        .array(ModelMeter)
         .describe("One entry for each of the five token kinds, in the order input, output, cache_read, cache_write, reasoning."),
 })
-    .describe("What requests to a model cost, as Billing prices them in the currency of the project's current billing account. These are list amounts before promotion codes, not a checkout guarantee; usage is billed afterwards under the service's subscription.\n\nEach token kind is priced on its own. `input` excludes cached input, which is `cache_read`, and `output` excludes reasoning the provider reports separately, which is `reasoning`; a request is billed for each kind it used.");
+    .describe("How requests to a model are billed: under the service's subscription, on the Billing plan `plan_id`, one rate for each token kind. Read the rates from Billing with `search-prices` for the plan and then `search-rates` with each meter's `dimensions`.\n\nEach token kind is priced on its own. `input` excludes cached input, which is `cache_read`, and `output` excludes reasoning the provider reports separately, which is `reasoning`; a request is billed for each kind it used.");

package/dist/canopy/v1/generated/validators/modelCapabilities.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modelCapabilities.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modelEndpoint.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modelEndpoint.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modelList.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modelList.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/modelListResponseBody.zod.d.ts

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
@@ -46,9 +46,9 @@ export declare const ModelListResponseBody: zod.ZodObject<{
         family: zod.ZodString;
         id: zod.ZodString;
         max_output_tokens: zod.ZodInt;
-        pricing: zod.ZodUnion<readonly [zod.ZodObject<{
-            currency: zod.ZodString;
-            token_kinds: zod.ZodArray<zod.ZodObject<{
+        billing: zod.ZodObject<{
+            plan_id: zod.ZodNullable<zod.ZodUUID>;
+            meters: zod.ZodArray<zod.ZodObject<{
                 token_kind: zod.ZodEnum<{
                     output: "output";
                     input: "input";
@@ -56,10 +56,10 @@ export declare const ModelListResponseBody: zod.ZodObject<{
                     cache_read: "cache_read";
                     cache_write: "cache_write";
                 }>;
-                unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-                unit_quantity: zod.ZodNullable<zod.ZodString>;
+                meter_lookup_key: zod.ZodString;
+                dimensions: zod.ZodRecord<zod.ZodString, zod.ZodString>;
             }, zod.z.core.$strict>>;
-        }, zod.z.core.$strict>, zod.ZodNull]>;
+        }, zod.z.core.$strict>;
         status: zod.ZodEnum<{
             available: "available";
             draining: "draining";

package/dist/canopy/v1/generated/validators/modelListResponseBody.zod.js

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,7 +35,7 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/validators/{tokenPrice.zod.d.ts → modelMeter.zod.d.ts}

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,11 +35,11 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-export declare const TokenPrice: zod.ZodObject<{
+export declare const ModelMeter: zod.ZodObject<{
     token_kind: zod.ZodEnum<{
         output: "output";
         input: "input";
@@ -47,8 +47,8 @@ export declare const TokenPrice: zod.ZodObject<{
         cache_read: "cache_read";
         cache_write: "cache_write";
     }>;
-    unit_amount: zod.ZodUnion<readonly [zod.ZodString, zod.ZodNull]>;
-    unit_quantity: zod.ZodNullable<zod.ZodString>;
+    meter_lookup_key: zod.ZodString;
+    dimensions: zod.ZodRecord<zod.ZodString, zod.ZodString>;
 }, zod.z.core.$strict>;
-export type TokenPrice = zod.input<typeof TokenPrice>;
-export type TokenPriceOutput = zod.output<typeof TokenPrice>;
+export type ModelMeter = zod.input<typeof ModelMeter>;
+export type ModelMeterOutput = zod.output<typeof ModelMeter>;

package/dist/canopy/v1/generated/validators/{tokenPrice.zod.js → modelMeter.zod.js}

@@ -16,7 +16,7 @@
  * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
  * through as written; a model's `capabilities` lists the values its upstream accepts.
  *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
@@ -35,18 +35,14 @@
  * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
  * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
  * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
+ * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-import { Money } from "./money.zod.js";
-export const TokenPrice = zod.strictObject({
+export const ModelMeter = zod.strictObject({
     token_kind: zod.enum(["input", "output", "cache_read", "cache_write", "reasoning"]),
-    unit_amount: zod
-        .union([Money, zod.null()])
-        .describe("The charge for `unit_quantity` tokens of this kind. Null when the kind has no rate in the currency, in which case the model cannot be billed for it."),
-    unit_quantity: zod
-        .string()
-        .nullable()
-        .describe("How many tokens `unit_amount` is for, such as `1000000`. Null when `unit_amount` is null."),
+    meter_lookup_key: zod.string(),
+    dimensions: zod
+        .record(zod.string(), zod.string())
+        .describe("The dimension values the usage of this token kind carries, and the rate is matched at."),
 });