@naturali/sdk 0.123.0 → 0.123.1

package/dist/index.cjs

@@ -4376,9 +4376,13 @@ var Users = class {
 	*
 	* Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made.
 	*
-	* **Nothing is refused against this.** The allowance is published, not enforced — an account past it keeps running. What does stop a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`.
+	* **On the `free` plan the allowance is enforced.** An account that has used it is refused `403 plan_limit_reached` with `resource: "runs"` on everything that starts a generation — on its own provider credential as much as on a managed model, because a run is a run — until the billing month turns or it upgrades. On `pro` and `business` nothing is refused: runs past the allowance are billed at the overage rate those plans are sold with. A contract plan is not counted.
 	*
-	* This read is more expensive than the balance one: it asks the meter once per project. Poll it on the order of minutes, not seconds.
+	* The other thing that stops a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`, and it never applies to your own credential.
+	*
+	* **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced.
+	*
+	* It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.
 	*
 	*/
 	static getCurrentUserUsage(options) {

package/dist/index.d.cts

@@ -6434,7 +6434,7 @@ type UserUsage = {
    */
   runs: number | null;
   /**
-   * Runs the account's plan includes per cycle. `null` on a contract plan, where the figure is commercial rather than published. Exceeding it refuses nothing today.
+   * Runs the account's plan includes per cycle. `null` on a contract plan, where the figure is commercial rather than published. Exceeding it is refused on `free` and billed as overage on `pro` and `business`.
    */
   runs_included: number | null;
   /**
@@ -21225,9 +21225,13 @@ declare class Users {
    *
    * Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made.
    *
-   * **Nothing is refused against this.** The allowance is published, not enforced — an account past it keeps running. What does stop a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`.
+   * **On the `free` plan the allowance is enforced.** An account that has used it is refused `403 plan_limit_reached` with `resource: "runs"` on everything that starts a generation — on its own provider credential as much as on a managed model, because a run is a run — until the billing month turns or it upgrades. On `pro` and `business` nothing is refused: runs past the allowance are billed at the overage rate those plans are sold with. A contract plan is not counted.
    *
-   * This read is more expensive than the balance one: it asks the meter once per project. Poll it on the order of minutes, not seconds.
+   * The other thing that stops a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`, and it never applies to your own credential.
+   *
+   * **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced.
+   *
+   * It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.
    *
    */
   static getCurrentUserUsage<ThrowOnError extends boolean = false>(options?: Options<GetCurrentUserUsageData, ThrowOnError>): RequestResult<GetCurrentUserUsageResponses, GetCurrentUserUsageErrors, ThrowOnError>;

package/dist/index.d.mts

@@ -6434,7 +6434,7 @@ type UserUsage = {
    */
   runs: number | null;
   /**
-   * Runs the account's plan includes per cycle. `null` on a contract plan, where the figure is commercial rather than published. Exceeding it refuses nothing today.
+   * Runs the account's plan includes per cycle. `null` on a contract plan, where the figure is commercial rather than published. Exceeding it is refused on `free` and billed as overage on `pro` and `business`.
    */
   runs_included: number | null;
   /**
@@ -21225,9 +21225,13 @@ declare class Users {
    *
    * Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made.
    *
-   * **Nothing is refused against this.** The allowance is published, not enforced — an account past it keeps running. What does stop a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`.
+   * **On the `free` plan the allowance is enforced.** An account that has used it is refused `403 plan_limit_reached` with `resource: "runs"` on everything that starts a generation — on its own provider credential as much as on a managed model, because a run is a run — until the billing month turns or it upgrades. On `pro` and `business` nothing is refused: runs past the allowance are billed at the overage rate those plans are sold with. A contract plan is not counted.
    *
-   * This read is more expensive than the balance one: it asks the meter once per project. Poll it on the order of minutes, not seconds.
+   * The other thing that stops a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`, and it never applies to your own credential.
+   *
+   * **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced.
+   *
+   * It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.
    *
    */
   static getCurrentUserUsage<ThrowOnError extends boolean = false>(options?: Options<GetCurrentUserUsageData, ThrowOnError>): RequestResult<GetCurrentUserUsageResponses, GetCurrentUserUsageErrors, ThrowOnError>;

package/dist/index.mjs

@@ -4375,9 +4375,13 @@ var Users = class {
 	*
 	* Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made.
 	*
-	* **Nothing is refused against this.** The allowance is published, not enforced — an account past it keeps running. What does stop a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`.
+	* **On the `free` plan the allowance is enforced.** An account that has used it is refused `403 plan_limit_reached` with `resource: "runs"` on everything that starts a generation — on its own provider credential as much as on a managed model, because a run is a run — until the billing month turns or it upgrades. On `pro` and `business` nothing is refused: runs past the allowance are billed at the overage rate those plans are sold with. A contract plan is not counted.
 	*
-	* This read is more expensive than the balance one: it asks the meter once per project. Poll it on the order of minutes, not seconds.
+	* The other thing that stops a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`, and it never applies to your own credential.
+	*
+	* **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced.
+	*
+	* It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.
 	*
 	*/
 	static getCurrentUserUsage(options) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/sdk",
-  "version": "0.123.0",
+  "version": "0.123.1",
   "description": "TypeScript SDK for the naturali.ai API, generated from its OpenAPI specs",
   "type": "module",
   "sideEffects": false,
@@ -37,7 +37,7 @@
     "tsx": "^4.23.1",
     "typescript": "~6.0.3",
     "vitest": "^4.1.10",
-    "@naturali/api": "0.123.0"
+    "@naturali/api": "0.123.1"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",