@omnibase/core-js 0.9.14 → 0.9.15

package/.openapi-generator/FILES

@@ -2,6 +2,7 @@
 .npmignore
 README.md
 docs/AcceptInvite200Response.md
+docs/AddSubscription200Response.md
 docs/ApiV1StorageDownloadPost200Response.md
 docs/ApiV1StorageObjectDelete200Response.md
 docs/ApiV1StorageUploadPost200Response.md
@@ -96,6 +97,8 @@ docs/RemoveSubscription200Response.md
 docs/SwitchActiveTenant200Response.md
 docs/TenantsAcceptInviteRequest.md
 docs/TenantsAcceptInviteResponse.md
+docs/TenantsAddSubscriptionRequest.md
+docs/TenantsAddSubscriptionResponse.md
 docs/TenantsAssignRoleRequest.md
 docs/TenantsAssignRoleResponse.md
 docs/TenantsCreateRoleRequest.md
@@ -159,6 +162,7 @@ src/apis/V1TenantsApi.ts
 src/apis/index.ts
 src/index.ts
 src/models/AcceptInvite200Response.ts
+src/models/AddSubscription200Response.ts
 src/models/ApiV1StorageDownloadPost200Response.ts
 src/models/ApiV1StorageObjectDelete200Response.ts
 src/models/ApiV1StorageUploadPost200Response.ts
@@ -253,6 +257,8 @@ src/models/RemoveSubscription200Response.ts
 src/models/SwitchActiveTenant200Response.ts
 src/models/TenantsAcceptInviteRequest.ts
 src/models/TenantsAcceptInviteResponse.ts
+src/models/TenantsAddSubscriptionRequest.ts
+src/models/TenantsAddSubscriptionResponse.ts
 src/models/TenantsAssignRoleRequest.ts
 src/models/TenantsAssignRoleResponse.ts
 src/models/TenantsCreateRoleRequest.ts

package/README.md

@@ -1,4 +1,4 @@
-# @omnibase/core-js@0.9.14
+# @omnibase/core-js@0.9.15
 
 A TypeScript SDK client for the api.omnibase.tech API.
 
@@ -79,6 +79,7 @@ All URIs are relative to *http://api.omnibase.tech*
 *V1StripeApi* | [**getStripeConfig**](docs/V1StripeApi.md#getstripeconfig) | **GET** /api/v1/stripe/config | Get public Stripe config
 *V1StripeApi* | [**getStripeConfigAdmin**](docs/V1StripeApi.md#getstripeconfigadmin) | **GET** /api/v1/stripe/config/admin | Get full Stripe config (admin)
 *V1TenantsApi* | [**acceptInvite**](docs/V1TenantsApi.md#acceptinvite) | **PUT** /api/v1/tenants/invites/accept | Accept tenant invite
+*V1TenantsApi* | [**addSubscription**](docs/V1TenantsApi.md#addsubscription) | **POST** /api/v1/payments/subscription/add | Add subscription
 *V1TenantsApi* | [**assignRole**](docs/V1TenantsApi.md#assignrole) | **POST** /api/v1/tenants/roles/assign/{user_id} | Assign role to user
 *V1TenantsApi* | [**createInvite**](docs/V1TenantsApi.md#createinvite) | **POST** /api/v1/tenants/invites | Create tenant invite
 *V1TenantsApi* | [**createRole**](docs/V1TenantsApi.md#createrole) | **POST** /api/v1/tenants/roles | Create role
@@ -102,6 +103,7 @@ All URIs are relative to *http://api.omnibase.tech*
 ### Models
 
 - [AcceptInvite200Response](docs/AcceptInvite200Response.md)
+- [AddSubscription200Response](docs/AddSubscription200Response.md)
 - [ApiV1StorageDownloadPost200Response](docs/ApiV1StorageDownloadPost200Response.md)
 - [ApiV1StorageObjectDelete200Response](docs/ApiV1StorageObjectDelete200Response.md)
 - [ApiV1StorageUploadPost200Response](docs/ApiV1StorageUploadPost200Response.md)
@@ -196,6 +198,8 @@ All URIs are relative to *http://api.omnibase.tech*
 - [SwitchActiveTenant200Response](docs/SwitchActiveTenant200Response.md)
 - [TenantsAcceptInviteRequest](docs/TenantsAcceptInviteRequest.md)
 - [TenantsAcceptInviteResponse](docs/TenantsAcceptInviteResponse.md)
+- [TenantsAddSubscriptionRequest](docs/TenantsAddSubscriptionRequest.md)
+- [TenantsAddSubscriptionResponse](docs/TenantsAddSubscriptionResponse.md)
 - [TenantsAssignRoleRequest](docs/TenantsAssignRoleRequest.md)
 - [TenantsAssignRoleResponse](docs/TenantsAssignRoleResponse.md)
 - [TenantsCreateRoleRequest](docs/TenantsCreateRoleRequest.md)
@@ -267,8 +271,8 @@ This TypeScript SDK client supports the [Fetch API](https://fetch.spec.whatwg.or
 and is automatically generated by the
 [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: `0.9.14`
-- Package version: `0.9.14`
+- API version: `0.9.15`
+- Package version: `0.9.15`
 - Generator version: `7.17.0`
 - Build package: `org.openapitools.codegen.languages.TypeScriptFetchClientCodegen`
 

package/dist/apis/V1AuthApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1AuthApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1ConfigurationApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1ConfigurationApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1PaymentsApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1PaymentsApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1PermissionsApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1PermissionsApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1StorageApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1StorageApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1StripeApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1StripeApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1TenantsApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,10 +10,13 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { AcceptInvite200Response, AssignRole200Response, CreateInvite200Response, CreateRole200Response, CreateSubscription200Response, CreateTenant200Response, DeleteRole200Response, DeleteTenant200Response, GetRoleDefinitions200Response, GetTenantBillingStatus200Response, GetTenantJWT200Response, HandlersSuccessResponse, ListRoles200Response, ListTenantSubscriptions200Response, ListTenantUsers200Response, RemoveSubscription200Response, SwitchActiveTenant200Response, TenantsAcceptInviteRequest, TenantsAssignRoleRequest, TenantsCreateRoleRequest, TenantsCreateSubscriptionRequest, TenantsCreateTenantRequest, TenantsCreateTenantUserInviteRequest, TenantsDeleteTenantUserRequest, TenantsRemoveSubscriptionRequest, TenantsSwitchTenantRequest, TenantsUpdateRoleRequest, TenantsUpdateTenantUserRoleRequest, UpdateTenantUserRole200Response } from '../models/index';
+import type { AcceptInvite200Response, AddSubscription200Response, AssignRole200Response, CreateInvite200Response, CreateRole200Response, CreateSubscription200Response, CreateTenant200Response, DeleteRole200Response, DeleteTenant200Response, GetRoleDefinitions200Response, GetTenantBillingStatus200Response, GetTenantJWT200Response, HandlersSuccessResponse, ListRoles200Response, ListTenantSubscriptions200Response, ListTenantUsers200Response, RemoveSubscription200Response, SwitchActiveTenant200Response, TenantsAcceptInviteRequest, TenantsAddSubscriptionRequest, TenantsAssignRoleRequest, TenantsCreateRoleRequest, TenantsCreateSubscriptionRequest, TenantsCreateTenantRequest, TenantsCreateTenantUserInviteRequest, TenantsDeleteTenantUserRequest, TenantsRemoveSubscriptionRequest, TenantsSwitchTenantRequest, TenantsUpdateRoleRequest, TenantsUpdateTenantUserRoleRequest, UpdateTenantUserRole200Response } from '../models/index';
 export interface AcceptInviteRequest {
     request: TenantsAcceptInviteRequest;
 }
+export interface AddSubscriptionRequest {
+    request: TenantsAddSubscriptionRequest;
+}
 export interface AssignRoleRequest {
     userId: string;
     request: TenantsAssignRoleRequest;
@@ -63,6 +66,16 @@ export declare class V1TenantsApi extends runtime.BaseAPI {
      * Accept tenant invite
      */
     acceptInvite(requestParameters: AcceptInviteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AcceptInvite200Response>;
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscriptionRaw(requestParameters: AddSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AddSubscription200Response>>;
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscription(requestParameters: AddSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AddSubscription200Response>;
     /**
      * Assigns a role to a user and creates all associated Keto relationships for the role\'s permissions.  ## Authentication Requires JWT token with tenant context and appropriate permissions.  ## Request Format Provide either `role_id` or `role_name` (not both).  ## Use Cases - Grant role to user - Assign permissions via role - User onboarding
      * Assign role to user

package/dist/apis/V1TenantsApi.js

@@ -5,7 +5,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -65,6 +65,42 @@ class V1TenantsApi extends runtime.BaseAPI {
             return yield response.value();
         });
     }
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscriptionRaw(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            if (requestParameters['request'] == null) {
+                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling addSubscription().');
+            }
+            const queryParameters = {};
+            const headerParameters = {};
+            headerParameters['Content-Type'] = 'application/json';
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
+            }
+            let urlPath = `/api/v1/payments/subscription/add`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+                body: (0, index_1.TenantsAddSubscriptionRequestToJSON)(requestParameters['request']),
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.AddSubscription200ResponseFromJSON)(jsonValue));
+        });
+    }
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscription(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.addSubscriptionRaw(requestParameters, initOverrides);
+            return yield response.value();
+        });
+    }
     /**
      * Assigns a role to a user and creates all associated Keto relationships for the role\'s permissions.  ## Authentication Requires JWT token with tenant context and appropriate permissions.  ## Request Format Provide either `role_id` or `role_name` (not both).  ## Use Cases - Grant role to user - Assign permissions via role - User onboarding
      * Assign role to user

package/dist/esm/apis/V1AuthApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1AuthApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1ConfigurationApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1ConfigurationApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1PaymentsApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1PaymentsApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1PermissionsApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1PermissionsApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1StorageApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1StorageApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1StripeApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1StripeApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1TenantsApi.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,10 +10,13 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { AcceptInvite200Response, AssignRole200Response, CreateInvite200Response, CreateRole200Response, CreateSubscription200Response, CreateTenant200Response, DeleteRole200Response, DeleteTenant200Response, GetRoleDefinitions200Response, GetTenantBillingStatus200Response, GetTenantJWT200Response, HandlersSuccessResponse, ListRoles200Response, ListTenantSubscriptions200Response, ListTenantUsers200Response, RemoveSubscription200Response, SwitchActiveTenant200Response, TenantsAcceptInviteRequest, TenantsAssignRoleRequest, TenantsCreateRoleRequest, TenantsCreateSubscriptionRequest, TenantsCreateTenantRequest, TenantsCreateTenantUserInviteRequest, TenantsDeleteTenantUserRequest, TenantsRemoveSubscriptionRequest, TenantsSwitchTenantRequest, TenantsUpdateRoleRequest, TenantsUpdateTenantUserRoleRequest, UpdateTenantUserRole200Response } from '../models/index';
+import type { AcceptInvite200Response, AddSubscription200Response, AssignRole200Response, CreateInvite200Response, CreateRole200Response, CreateSubscription200Response, CreateTenant200Response, DeleteRole200Response, DeleteTenant200Response, GetRoleDefinitions200Response, GetTenantBillingStatus200Response, GetTenantJWT200Response, HandlersSuccessResponse, ListRoles200Response, ListTenantSubscriptions200Response, ListTenantUsers200Response, RemoveSubscription200Response, SwitchActiveTenant200Response, TenantsAcceptInviteRequest, TenantsAddSubscriptionRequest, TenantsAssignRoleRequest, TenantsCreateRoleRequest, TenantsCreateSubscriptionRequest, TenantsCreateTenantRequest, TenantsCreateTenantUserInviteRequest, TenantsDeleteTenantUserRequest, TenantsRemoveSubscriptionRequest, TenantsSwitchTenantRequest, TenantsUpdateRoleRequest, TenantsUpdateTenantUserRoleRequest, UpdateTenantUserRole200Response } from '../models/index';
 export interface AcceptInviteRequest {
     request: TenantsAcceptInviteRequest;
 }
+export interface AddSubscriptionRequest {
+    request: TenantsAddSubscriptionRequest;
+}
 export interface AssignRoleRequest {
     userId: string;
     request: TenantsAssignRoleRequest;
@@ -63,6 +66,16 @@ export declare class V1TenantsApi extends runtime.BaseAPI {
      * Accept tenant invite
      */
     acceptInvite(requestParameters: AcceptInviteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AcceptInvite200Response>;
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscriptionRaw(requestParameters: AddSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<AddSubscription200Response>>;
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscription(requestParameters: AddSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<AddSubscription200Response>;
     /**
      * Assigns a role to a user and creates all associated Keto relationships for the role\'s permissions.  ## Authentication Requires JWT token with tenant context and appropriate permissions.  ## Request Format Provide either `role_id` or `role_name` (not both).  ## Use Cases - Grant role to user - Assign permissions via role - User onboarding
      * Assign role to user

package/dist/esm/apis/V1TenantsApi.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -21,7 +21,7 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 import * as runtime from '../runtime';
-import { AcceptInvite200ResponseFromJSON, AssignRole200ResponseFromJSON, CreateInvite200ResponseFromJSON, CreateRole200ResponseFromJSON, CreateSubscription200ResponseFromJSON, CreateTenant200ResponseFromJSON, DeleteRole200ResponseFromJSON, DeleteTenant200ResponseFromJSON, GetRoleDefinitions200ResponseFromJSON, GetTenantBillingStatus200ResponseFromJSON, GetTenantJWT200ResponseFromJSON, HandlersSuccessResponseFromJSON, ListRoles200ResponseFromJSON, ListTenantSubscriptions200ResponseFromJSON, ListTenantUsers200ResponseFromJSON, RemoveSubscription200ResponseFromJSON, SwitchActiveTenant200ResponseFromJSON, TenantsAcceptInviteRequestToJSON, TenantsAssignRoleRequestToJSON, TenantsCreateRoleRequestToJSON, TenantsCreateSubscriptionRequestToJSON, TenantsCreateTenantRequestToJSON, TenantsCreateTenantUserInviteRequestToJSON, TenantsDeleteTenantUserRequestToJSON, TenantsRemoveSubscriptionRequestToJSON, TenantsSwitchTenantRequestToJSON, TenantsUpdateRoleRequestToJSON, TenantsUpdateTenantUserRoleRequestToJSON, UpdateTenantUserRole200ResponseFromJSON, } from '../models/index';
+import { AcceptInvite200ResponseFromJSON, AddSubscription200ResponseFromJSON, AssignRole200ResponseFromJSON, CreateInvite200ResponseFromJSON, CreateRole200ResponseFromJSON, CreateSubscription200ResponseFromJSON, CreateTenant200ResponseFromJSON, DeleteRole200ResponseFromJSON, DeleteTenant200ResponseFromJSON, GetRoleDefinitions200ResponseFromJSON, GetTenantBillingStatus200ResponseFromJSON, GetTenantJWT200ResponseFromJSON, HandlersSuccessResponseFromJSON, ListRoles200ResponseFromJSON, ListTenantSubscriptions200ResponseFromJSON, ListTenantUsers200ResponseFromJSON, RemoveSubscription200ResponseFromJSON, SwitchActiveTenant200ResponseFromJSON, TenantsAcceptInviteRequestToJSON, TenantsAddSubscriptionRequestToJSON, TenantsAssignRoleRequestToJSON, TenantsCreateRoleRequestToJSON, TenantsCreateSubscriptionRequestToJSON, TenantsCreateTenantRequestToJSON, TenantsCreateTenantUserInviteRequestToJSON, TenantsDeleteTenantUserRequestToJSON, TenantsRemoveSubscriptionRequestToJSON, TenantsSwitchTenantRequestToJSON, TenantsUpdateRoleRequestToJSON, TenantsUpdateTenantUserRoleRequestToJSON, UpdateTenantUserRole200ResponseFromJSON, } from '../models/index';
 /**
  *
  */
@@ -62,6 +62,42 @@ export class V1TenantsApi extends runtime.BaseAPI {
             return yield response.value();
         });
     }
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscriptionRaw(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            if (requestParameters['request'] == null) {
+                throw new runtime.RequiredError('request', 'Required parameter "request" was null or undefined when calling addSubscription().');
+            }
+            const queryParameters = {};
+            const headerParameters = {};
+            headerParameters['Content-Type'] = 'application/json';
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
+            }
+            let urlPath = `/api/v1/payments/subscription/add`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+                body: TenantsAddSubscriptionRequestToJSON(requestParameters['request']),
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => AddSubscription200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Adds a Stripe subscription for the authenticated tenant using the provided plan ID.  ## Authentication Requires JWT token with tenant context.  ## Request Parameters - **plan_id** (required): The configuration item ID (e.g., \"neon_compute_starter\") that maps to a Stripe price - **stripe_customer_id** (optional): Override tenant\'s Stripe customer ID if needed  ## Process Flow 1. Validates the plan_id and maps it to a Stripe price_id via the stripe_id_mappings table 2. Resolves the Stripe customer ID from the authenticated tenant (or uses provided stripe_customer_id) 3. Checks if subscription already exists for this plan to prevent duplicates 4. Creates the subscription in Stripe with the specified price 5. Returns the subscription ID and status  ## Notes - If a subscription for this plan already exists, returns a 400 error - The subscription is created immediately and begins billing  ## Use Cases - Subscribe tenant to metered pricing plans (compute, storage, workers) - Enable usage-based billing for resources - Add additional services to tenant\'s billing
+     * Add subscription
+     */
+    addSubscription(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.addSubscriptionRaw(requestParameters, initOverrides);
+            return yield response.value();
+        });
+    }
     /**
      * Assigns a role to a user and creates all associated Keto relationships for the role\'s permissions.  ## Authentication Requires JWT token with tenant context and appropriate permissions.  ## Request Format Provide either `role_id` or `role_name` (not both).  ## Use Cases - Grant role to user - Assign permissions via role - User onboarding
      * Assign role to user

package/dist/esm/models/AcceptInvite200Response.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/AcceptInvite200Response.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.14
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).