@leaflow/sdk 0.132.0 → 0.134.0

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

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

@@ -16,7 +16,7 @@
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
  *
  * ## Conventions
  *

package/dist/compute/v1/generated/models.d.ts

@@ -211,12 +211,13 @@ export interface BillingChoice {
     termination_policy?: TerminationPolicy;
 }
 /**
- * automatic confirms checkout with applicable account discounts and collects payment from eligible
- * credit grants and available balance. Insufficient funds fail the purchase with HTTP 422
+ * automatic applies the best applicable account discount, issues the invoice and pays it from eligible
+ * credit grants and available balance at placement. Insufficient funds fail the purchase with HTTP 422
  * BILLING_INSUFFICIENT_FUNDS; no Billing order, charge or discount redemption is committed.
- * deferred creates a pending_checkout order for subsequent confirmation and payment through Billing.
- * No new discount redemption or payment is made when the order is created. An order whose total is
- * zero, with nothing to pay or discount, completes checkout at placement in either mode.
+ * deferred places the order with a draft invoice at base prices and collects nothing. Paying that
+ * invoice through Billing applies a promotion code or the best applicable account discount, issues the
+ * invoice and collects it; an order still unpaid at its deadline expires. A zero-total invoice is issued
+ * and paid at placement in either mode.
  */
 export type CheckoutMode = (typeof CheckoutMode)[keyof typeof CheckoutMode];
 export declare const CheckoutMode: {
@@ -238,7 +239,7 @@ export type Money = string;
 /**
  * Shared checkout choices for a product purchase. Omitting this object or mode selects
  * automatic checkout. Each purchase creates its own order. Promotion codes are supplied only to
- * Billing quote and checkout operations. A service may retain a failed creation record when Billing
+ * Billing quote and payment operations. A service may retain a failed creation record when Billing
  * refuses a purchase; no infrastructure is created for that refusal.
  */
 export interface CheckoutOptions {
@@ -247,7 +248,7 @@ export interface CheckoutOptions {
      * Expected invoice total after discounts and tax, before applying credit grants or balance.
      * A different total fails with BILLING_AMOUNT_CHANGED without charging or reserving a discount.
      * Accepted only in automatic mode; with deferred it is refused with HTTP 400. For deferred
-     * checkout, confirm the amount through Billing.
+     * checkout, give the expected amount when paying the invoice through Billing.
      */
     expected_amount?: Money & string;
 }

package/dist/compute/v1/generated/validators/checkoutMode.zod.js

@@ -24,4 +24,4 @@
 import * as zod from "zod";
 export const CheckoutMode = zod
     .enum(["automatic", "deferred"])
-    .describe("automatic confirms checkout with applicable account discounts and collects payment from eligible\ncredit grants and available balance. Insufficient funds fail the purchase with HTTP 422\nBILLING_INSUFFICIENT_FUNDS; no Billing order, charge or discount redemption is committed.\ndeferred creates a pending_checkout order for subsequent confirmation and payment through Billing.\nNo new discount redemption or payment is made when the order is created. An order whose total is\nzero, with nothing to pay or discount, completes checkout at placement in either mode.");
+    .describe("automatic applies the best applicable account discount, issues the invoice and pays it from eligible\ncredit grants and available balance at placement. Insufficient funds fail the purchase with HTTP 422\nBILLING_INSUFFICIENT_FUNDS; no Billing order, charge or discount redemption is committed.\ndeferred places the order with a draft invoice at base prices and collects nothing. Paying that\ninvoice through Billing applies a promotion code or the best applicable account discount, issues the\ninvoice and collects it; an order still unpaid at its deadline expires. A zero-total invoice is issued\nand paid at placement in either mode.");

package/dist/compute/v1/generated/validators/checkoutOptions.zod.js

@@ -31,6 +31,6 @@ export const CheckoutOptions = zod
     mode: CheckoutMode.default(checkoutOptionsModeDefault),
     expected_amount: Money.and(zod.string().regex(checkoutOptionsExpectedAmountTwoRegExp))
         .optional()
-        .describe("Expected invoice total after discounts and tax, before applying credit grants or balance.\nA different total fails with BILLING_AMOUNT_CHANGED without charging or reserving a discount.\nAccepted only in automatic mode; with deferred it is refused with HTTP 400. For deferred\ncheckout, confirm the amount through Billing."),
+        .describe("Expected invoice total after discounts and tax, before applying credit grants or balance.\nA different total fails with BILLING_AMOUNT_CHANGED without charging or reserving a discount.\nAccepted only in automatic mode; with deferred it is refused with HTTP 400. For deferred\ncheckout, give the expected amount when paying the invoice through Billing."),
 })
-    .describe("Shared checkout choices for a product purchase. Omitting this object or mode selects\nautomatic checkout. Each purchase creates its own order. Promotion codes are supplied only to\nBilling quote and checkout operations. A service may retain a failed creation record when Billing\nrefuses a purchase; no infrastructure is created for that refusal.");
+    .describe("Shared checkout choices for a product purchase. Omitting this object or mode selects\nautomatic checkout. Each purchase creates its own order. Promotion codes are supplied only to\nBilling quote and payment operations. A service may retain a failed creation record when Billing\nrefuses a purchase; no infrastructure is created for that refusal.");

package/dist/index.d.ts

@@ -1,6 +1,7 @@
 export * as account from "./account/v1/index.js";
 export * as assistant from "./assistant/v1/index.js";
 export * as billing from "./billing/v1/index.js";
+export * as canopyInference from "./canopy/inference/v1/index.js";
 export * as canopy from "./canopy/v1/index.js";
 export * as compute from "./compute/v1/index.js";
 export * as dns from "./dns/v1/index.js";

package/dist/index.js

@@ -1,6 +1,7 @@
 export * as account from "./account/v1/index.js";
 export * as assistant from "./assistant/v1/index.js";
 export * as billing from "./billing/v1/index.js";
+export * as canopyInference from "./canopy/inference/v1/index.js";
 export * as canopy from "./canopy/v1/index.js";
 export * as compute from "./compute/v1/index.js";
 export * as dns from "./dns/v1/index.js";

package/dist/routes.d.ts

@@ -1110,6 +1110,38 @@ export declare const routes: readonly [{
     readonly operationId: "get-statement-usage";
     readonly securityScheme: "AccessToken";
     readonly upstreamUrl: "https://billing.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy/inference";
+    readonly method: "POST";
+    readonly path: "/v1/chat/completions";
+    readonly operationId: "create-chat-completion";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy/inference";
+    readonly method: "POST";
+    readonly path: "/v1/embeddings";
+    readonly operationId: "create-embeddings";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy/inference";
+    readonly method: "GET";
+    readonly path: "/v1/models";
+    readonly operationId: "list-inference-models";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy/inference";
+    readonly method: "GET";
+    readonly path: "/v1/models/{model}";
+    readonly operationId: "get-inference-model";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
 }, {
     readonly service: "canopy";
     readonly contract: "canopy";

package/dist/routes.js

@@ -1251,6 +1251,42 @@ export const routes = [
         securityScheme: "AccessToken",
         upstreamUrl: "https://billing.leaflow.cloud",
     },
+    {
+        service: "canopy",
+        contract: "canopy/inference",
+        method: "POST",
+        path: "/v1/chat/completions",
+        operationId: "create-chat-completion",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
+    {
+        service: "canopy",
+        contract: "canopy/inference",
+        method: "POST",
+        path: "/v1/embeddings",
+        operationId: "create-embeddings",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
+    {
+        service: "canopy",
+        contract: "canopy/inference",
+        method: "GET",
+        path: "/v1/models",
+        operationId: "list-inference-models",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
+    {
+        service: "canopy",
+        contract: "canopy/inference",
+        method: "GET",
+        path: "/v1/models/{model}",
+        operationId: "get-inference-model",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
     {
         service: "canopy",
         contract: "canopy",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.132.0",
+  "version": "0.134.0",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {