@omnibase/core-js 0.9.10 → 0.9.12

package/.openapi-generator/FILES

@@ -1,6 +1,5 @@
 .gitignore
 .npmignore
-.openapi-generator-ignore
 README.md
 docs/AcceptInvite200Response.md
 docs/ApiV1StorageDownloadPost200Response.md
@@ -24,6 +23,7 @@ docs/CreateCustomerPortal200Response.md
 docs/CreateInvite200Response.md
 docs/CreateRelationship200Response.md
 docs/CreateRole200Response.md
+docs/CreateSubscription200Response.md
 docs/CreateTenant200Response.md
 docs/DeleteRole200Response.md
 docs/DeleteTenant200Response.md
@@ -119,6 +119,8 @@ docs/V1CreatePortalRequest.md
 docs/V1CreatePortalResponse.md
 docs/V1CreateRelationshipRequest.md
 docs/V1CreateRelationshipResponse.md
+docs/V1CreateSubscriptionRequest.md
+docs/V1CreateSubscriptionResponse.md
 docs/V1DatabaseApi.md
 docs/V1MigrationErrorResponse.md
 docs/V1MigrationSuccessResponse.md
@@ -164,6 +166,7 @@ src/models/CreateCustomerPortal200Response.ts
 src/models/CreateInvite200Response.ts
 src/models/CreateRelationship200Response.ts
 src/models/CreateRole200Response.ts
+src/models/CreateSubscription200Response.ts
 src/models/CreateTenant200Response.ts
 src/models/DeleteRole200Response.ts
 src/models/DeleteTenant200Response.ts
@@ -258,6 +261,8 @@ src/models/V1CreatePortalRequest.ts
 src/models/V1CreatePortalResponse.ts
 src/models/V1CreateRelationshipRequest.ts
 src/models/V1CreateRelationshipResponse.ts
+src/models/V1CreateSubscriptionRequest.ts
+src/models/V1CreateSubscriptionResponse.ts
 src/models/V1MigrationErrorResponse.ts
 src/models/V1MigrationSuccessResponse.ts
 src/models/V1NamespaceDeploymentResponse.ts

package/README.md

@@ -1,4 +1,4 @@
-# @omnibase/core-js@0.9.10
+# @omnibase/core-js@0.9.12
 
 A TypeScript SDK client for the api.omnibase.tech API.
 
@@ -58,6 +58,7 @@ All URIs are relative to *http://api.omnibase.tech*
 *V1DatabaseApi* | [**uploadDatabaseMigrations**](docs/V1DatabaseApi.md#uploaddatabasemigrations) | **POST** /api/v1/database/migrations | Upload database migrations
 *V1PaymentsApi* | [**createCheckout**](docs/V1PaymentsApi.md#createcheckout) | **POST** /api/v1/payments/checkout | Create checkout session
 *V1PaymentsApi* | [**createCustomerPortal**](docs/V1PaymentsApi.md#createcustomerportal) | **POST** /api/v1/payments/portal | Create customer portal session
+*V1PaymentsApi* | [**createSubscription**](docs/V1PaymentsApi.md#createsubscription) | **POST** /api/v1/payments/subscription | Create subscription
 *V1PaymentsApi* | [**recordUsage**](docs/V1PaymentsApi.md#recordusage) | **POST** /api/v1/payments/usage | Record metered usage
 *V1PermissionsApi* | [**checkPermission**](docs/V1PermissionsApi.md#checkpermission) | **POST** /api/v1/permissions/check | Check permission
 *V1PermissionsApi* | [**createRelationship**](docs/V1PermissionsApi.md#createrelationship) | **POST** /api/v1/permissions/relationships | Create relationship
@@ -116,6 +117,7 @@ All URIs are relative to *http://api.omnibase.tech*
 - [CreateInvite200Response](docs/CreateInvite200Response.md)
 - [CreateRelationship200Response](docs/CreateRelationship200Response.md)
 - [CreateRole200Response](docs/CreateRole200Response.md)
+- [CreateSubscription200Response](docs/CreateSubscription200Response.md)
 - [CreateTenant200Response](docs/CreateTenant200Response.md)
 - [DeleteRole200Response](docs/DeleteRole200Response.md)
 - [DeleteTenant200Response](docs/DeleteTenant200Response.md)
@@ -210,6 +212,8 @@ All URIs are relative to *http://api.omnibase.tech*
 - [V1CreatePortalResponse](docs/V1CreatePortalResponse.md)
 - [V1CreateRelationshipRequest](docs/V1CreateRelationshipRequest.md)
 - [V1CreateRelationshipResponse](docs/V1CreateRelationshipResponse.md)
+- [V1CreateSubscriptionRequest](docs/V1CreateSubscriptionRequest.md)
+- [V1CreateSubscriptionResponse](docs/V1CreateSubscriptionResponse.md)
 - [V1MigrationErrorResponse](docs/V1MigrationErrorResponse.md)
 - [V1MigrationSuccessResponse](docs/V1MigrationSuccessResponse.md)
 - [V1NamespaceDeploymentResponse](docs/V1NamespaceDeploymentResponse.md)
@@ -243,8 +247,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.10`
-- Package version: `0.9.10`
+- API version: `0.9.12`
+- Package version: `0.9.12`
 - 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1DatabaseApi.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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1DatabaseApi.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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,13 +10,16 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { CreateCheckout200Response, CreateCustomerPortal200Response, HandlersSuccessResponse, V1CreateCheckoutRequest, V1CreatePortalRequest, V1RecordUsageRequest } from '../models/index';
+import type { CreateCheckout200Response, CreateCustomerPortal200Response, CreateSubscription200Response, HandlersSuccessResponse, V1CreateCheckoutRequest, V1CreatePortalRequest, V1CreateSubscriptionRequest, V1RecordUsageRequest } from '../models/index';
 export interface CreateCheckoutRequest {
     request: V1CreateCheckoutRequest;
 }
 export interface CreateCustomerPortalRequest {
     request: V1CreatePortalRequest;
 }
+export interface CreateSubscriptionRequest {
+    request: V1CreateSubscriptionRequest;
+}
 export interface RecordUsageRequest {
     request: V1RecordUsageRequest;
 }
@@ -44,6 +47,16 @@ export declare class V1PaymentsApi extends runtime.BaseAPI {
      * Create customer portal session
      */
     createCustomerPortal(requestParameters: CreateCustomerPortalRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<CreateCustomerPortal200Response>;
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscriptionRaw(requestParameters: CreateSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<CreateSubscription200Response>>;
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscription(requestParameters: CreateSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<CreateSubscription200Response>;
     /**
      * Records a usage event for metered billing. The customer must have an active subscription with metered pricing.  ## Authentication Requires JWT token and an associated Stripe customer ID.  ## Use Cases - API request metering - Compute time tracking - Storage usage recording - Any metered billing scenario
      * Record metered usage

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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -101,6 +101,39 @@ class V1PaymentsApi extends runtime.BaseAPI {
             return yield response.value();
         });
     }
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscriptionRaw(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 createSubscription().');
+            }
+            const queryParameters = {};
+            const headerParameters = {};
+            headerParameters['Content-Type'] = 'application/json';
+            let urlPath = `/api/v1/payments/subscription`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+                body: (0, index_1.V1CreateSubscriptionRequestToJSON)(requestParameters['request']),
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.CreateSubscription200ResponseFromJSON)(jsonValue));
+        });
+    }
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscription(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.createSubscriptionRaw(requestParameters, initOverrides);
+            return yield response.value();
+        });
+    }
     /**
      * Records a usage event for metered billing. The customer must have an active subscription with metered pricing.  ## Authentication Requires JWT token and an associated Stripe customer ID.  ## Use Cases - API request metering - Compute time tracking - Storage usage recording - Any metered billing scenario
      * Record metered usage

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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1DatabaseApi.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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/apis/V1DatabaseApi.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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,13 +10,16 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { CreateCheckout200Response, CreateCustomerPortal200Response, HandlersSuccessResponse, V1CreateCheckoutRequest, V1CreatePortalRequest, V1RecordUsageRequest } from '../models/index';
+import type { CreateCheckout200Response, CreateCustomerPortal200Response, CreateSubscription200Response, HandlersSuccessResponse, V1CreateCheckoutRequest, V1CreatePortalRequest, V1CreateSubscriptionRequest, V1RecordUsageRequest } from '../models/index';
 export interface CreateCheckoutRequest {
     request: V1CreateCheckoutRequest;
 }
 export interface CreateCustomerPortalRequest {
     request: V1CreatePortalRequest;
 }
+export interface CreateSubscriptionRequest {
+    request: V1CreateSubscriptionRequest;
+}
 export interface RecordUsageRequest {
     request: V1RecordUsageRequest;
 }
@@ -44,6 +47,16 @@ export declare class V1PaymentsApi extends runtime.BaseAPI {
      * Create customer portal session
      */
     createCustomerPortal(requestParameters: CreateCustomerPortalRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<CreateCustomerPortal200Response>;
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscriptionRaw(requestParameters: CreateSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<CreateSubscription200Response>>;
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscription(requestParameters: CreateSubscriptionRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<CreateSubscription200Response>;
     /**
      * Records a usage event for metered billing. The customer must have an active subscription with metered pricing.  ## Authentication Requires JWT token and an associated Stripe customer ID.  ## Use Cases - API request metering - Compute time tracking - Storage usage recording - Any metered billing scenario
      * Record metered usage

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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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 { CreateCheckout200ResponseFromJSON, CreateCustomerPortal200ResponseFromJSON, HandlersSuccessResponseFromJSON, V1CreateCheckoutRequestToJSON, V1CreatePortalRequestToJSON, V1RecordUsageRequestToJSON, } from '../models/index';
+import { CreateCheckout200ResponseFromJSON, CreateCustomerPortal200ResponseFromJSON, CreateSubscription200ResponseFromJSON, HandlersSuccessResponseFromJSON, V1CreateCheckoutRequestToJSON, V1CreatePortalRequestToJSON, V1CreateSubscriptionRequestToJSON, V1RecordUsageRequestToJSON, } from '../models/index';
 /**
  *
  */
@@ -98,6 +98,39 @@ export class V1PaymentsApi extends runtime.BaseAPI {
             return yield response.value();
         });
     }
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscriptionRaw(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 createSubscription().');
+            }
+            const queryParameters = {};
+            const headerParameters = {};
+            headerParameters['Content-Type'] = 'application/json';
+            let urlPath = `/api/v1/payments/subscription`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+                body: V1CreateSubscriptionRequestToJSON(requestParameters['request']),
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => CreateSubscription200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Creates a Stripe subscription for a customer. Provide either tenant_id (to lookup customer from database) OR stripe_customer_id (to use directly).  ## Authentication Requires valid API authentication.  ## Customer Identification - If stripe_customer_id is provided, it will be used directly - If tenant_id is provided, the tenant\'s stripe_customer_id will be looked up from auth.tenants table - At least one of tenant_id or stripe_customer_id must be provided  ## Use Cases - Subscribe tenant to metered pricing plans - Upgrade/downgrade tenant plans - Enable usage-based billing for resources - Direct subscription creation with Stripe customer ID
+     * Create subscription
+     */
+    createSubscription(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.createSubscriptionRaw(requestParameters, initOverrides);
+            return yield response.value();
+        });
+    }
     /**
      * Records a usage event for metered billing. The customer must have an active subscription with metered pricing.  ## Authentication Requires JWT token and an associated Stripe customer ID.  ## Use Cases - API request metering - Compute time tracking - Storage usage recording - Any metered billing scenario
      * Record metered usage

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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

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.10
+ * The version of the OpenAPI document: 0.9.12
  * 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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/ApiV1StorageDownloadPost200Response.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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/ApiV1StorageDownloadPost200Response.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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/ApiV1StorageObjectDelete200Response.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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/ApiV1StorageObjectDelete200Response.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.10
+ * The version of the OpenAPI document: 0.9.12
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).