@omnibase/core-js 0.9.5 → 0.9.8

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.5
+ * The version of the OpenAPI document: 0.9.8
  * 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.5
+ * The version of the OpenAPI document: 0.9.8
  * 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.5
+ * The version of the OpenAPI document: 0.9.8
  * 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.5
+ * The version of the OpenAPI document: 0.9.8
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,7 +10,7 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { ApiV1AuthActiveTenantGet200Response, ApiV1AuthIdentityGet200Response, ApiV1AuthLogoutPost200Response, ApiV1AuthSessionGet200Response, ApiV1AuthWhoamiGet200Response } from '../models/index';
+import type { GetActiveTenant200Response, GetIdentity200Response, GetSession200Response, ListTenants200Response, Logout200Response, WhoAmI200Response } from '../models/index';
 /**
  *
  */
@@ -19,50 +19,60 @@ export declare class V1AuthApi extends runtime.BaseAPI {
      * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
      * Get active tenant
      */
-    apiV1AuthActiveTenantGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthActiveTenantGet200Response>>;
+    getActiveTenantRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetActiveTenant200Response>>;
     /**
      * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
      * Get active tenant
      */
-    apiV1AuthActiveTenantGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthActiveTenantGet200Response>;
+    getActiveTenant(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetActiveTenant200Response>;
     /**
      * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
      * Get current identity
      */
-    apiV1AuthIdentityGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthIdentityGet200Response>>;
+    getIdentityRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetIdentity200Response>>;
     /**
      * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
      * Get current identity
      */
-    apiV1AuthIdentityGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthIdentityGet200Response>;
-    /**
-     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
-     * Logout user
-     */
-    apiV1AuthLogoutPostRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthLogoutPost200Response>>;
-    /**
-     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
-     * Logout user
-     */
-    apiV1AuthLogoutPost(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthLogoutPost200Response>;
+    getIdentity(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetIdentity200Response>;
     /**
      * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
      * Get current session
      */
-    apiV1AuthSessionGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthSessionGet200Response>>;
+    getSessionRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetSession200Response>>;
     /**
      * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
      * Get current session
      */
-    apiV1AuthSessionGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthSessionGet200Response>;
+    getSession(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetSession200Response>;
+    /**
+     * Returns all tenants the user is a member of with their active status.  ## Tenant Memberships Users can be members of multiple tenants. Each membership has: - Active status (only one tenant can be active at a time) - Full tenant information (ID, name, type, etc.)  ## Use Case Display tenant switcher UI or list all organizations the user belongs to.
+     * List user\'s tenants
+     */
+    listTenantsRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ListTenants200Response>>;
+    /**
+     * Returns all tenants the user is a member of with their active status.  ## Tenant Memberships Users can be members of multiple tenants. Each membership has: - Active status (only one tenant can be active at a time) - Full tenant information (ID, name, type, etc.)  ## Use Case Display tenant switcher UI or list all organizations the user belongs to.
+     * List user\'s tenants
+     */
+    listTenants(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ListTenants200Response>;
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    logoutRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Logout200Response>>;
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    logout(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Logout200Response>;
     /**
      * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
      * Check authentication status
      */
-    apiV1AuthWhoamiGetRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ApiV1AuthWhoamiGet200Response>>;
+    whoAmIRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<WhoAmI200Response>>;
     /**
      * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
      * Check authentication status
      */
-    apiV1AuthWhoamiGet(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ApiV1AuthWhoamiGet200Response>;
+    whoAmI(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<WhoAmI200Response>;
 }

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.5
+ * The version of the OpenAPI document: 0.9.8
  * 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 { ApiV1AuthActiveTenantGet200ResponseFromJSON, ApiV1AuthIdentityGet200ResponseFromJSON, ApiV1AuthLogoutPost200ResponseFromJSON, ApiV1AuthSessionGet200ResponseFromJSON, ApiV1AuthWhoamiGet200ResponseFromJSON, } from '../models/index';
+import { GetActiveTenant200ResponseFromJSON, GetIdentity200ResponseFromJSON, GetSession200ResponseFromJSON, ListTenants200ResponseFromJSON, Logout200ResponseFromJSON, WhoAmI200ResponseFromJSON, } from '../models/index';
 /**
  *
  */
@@ -30,7 +30,7 @@ export class V1AuthApi extends runtime.BaseAPI {
      * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
      * Get active tenant
      */
-    apiV1AuthActiveTenantGetRaw(initOverrides) {
+    getActiveTenantRaw(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             const queryParameters = {};
             const headerParameters = {};
@@ -44,16 +44,16 @@ export class V1AuthApi extends runtime.BaseAPI {
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthActiveTenantGet200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => GetActiveTenant200ResponseFromJSON(jsonValue));
         });
     }
     /**
      * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
      * Get active tenant
      */
-    apiV1AuthActiveTenantGet(initOverrides) {
+    getActiveTenant(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.apiV1AuthActiveTenantGetRaw(initOverrides);
+            const response = yield this.getActiveTenantRaw(initOverrides);
             return yield response.value();
         });
     }
@@ -61,7 +61,7 @@ export class V1AuthApi extends runtime.BaseAPI {
      * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
      * Get current identity
      */
-    apiV1AuthIdentityGetRaw(initOverrides) {
+    getIdentityRaw(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             const queryParameters = {};
             const headerParameters = {};
@@ -75,78 +75,109 @@ export class V1AuthApi extends runtime.BaseAPI {
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthIdentityGet200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => GetIdentity200ResponseFromJSON(jsonValue));
         });
     }
     /**
      * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
      * Get current identity
      */
-    apiV1AuthIdentityGet(initOverrides) {
+    getIdentity(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.apiV1AuthIdentityGetRaw(initOverrides);
+            const response = yield this.getIdentityRaw(initOverrides);
             return yield response.value();
         });
     }
     /**
-     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
-     * Logout user
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
      */
-    apiV1AuthLogoutPostRaw(initOverrides) {
+    getSessionRaw(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             const queryParameters = {};
             const headerParameters = {};
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/api/v1/auth/logout`;
+            let urlPath = `/api/v1/auth/session`;
             const response = yield this.request({
                 path: urlPath,
-                method: 'POST',
+                method: 'GET',
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthLogoutPost200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => GetSession200ResponseFromJSON(jsonValue));
         });
     }
     /**
-     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
-     * Logout user
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
      */
-    apiV1AuthLogoutPost(initOverrides) {
+    getSession(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.apiV1AuthLogoutPostRaw(initOverrides);
+            const response = yield this.getSessionRaw(initOverrides);
             return yield response.value();
         });
     }
     /**
-     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
-     * Get current session
+     * Returns all tenants the user is a member of with their active status.  ## Tenant Memberships Users can be members of multiple tenants. Each membership has: - Active status (only one tenant can be active at a time) - Full tenant information (ID, name, type, etc.)  ## Use Case Display tenant switcher UI or list all organizations the user belongs to.
+     * List user\'s tenants
      */
-    apiV1AuthSessionGetRaw(initOverrides) {
+    listTenantsRaw(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             const queryParameters = {};
             const headerParameters = {};
             if (this.configuration && this.configuration.apiKey) {
                 headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
             }
-            let urlPath = `/api/v1/auth/session`;
+            let urlPath = `/api/v1/auth/tenants`;
             const response = yield this.request({
                 path: urlPath,
                 method: 'GET',
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthSessionGet200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => ListTenants200ResponseFromJSON(jsonValue));
         });
     }
     /**
-     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
-     * Get current session
+     * Returns all tenants the user is a member of with their active status.  ## Tenant Memberships Users can be members of multiple tenants. Each membership has: - Active status (only one tenant can be active at a time) - Full tenant information (ID, name, type, etc.)  ## Use Case Display tenant switcher UI or list all organizations the user belongs to.
+     * List user\'s tenants
+     */
+    listTenants(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const response = yield this.listTenantsRaw(initOverrides);
+            return yield response.value();
+        });
+    }
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    logoutRaw(initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.apiKey) {
+                headerParameters["Cookie"] = yield this.configuration.apiKey("Cookie"); // SessionAuth authentication
+            }
+            let urlPath = `/api/v1/auth/logout`;
+            const response = yield this.request({
+                path: urlPath,
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.JSONApiResponse(response, (jsonValue) => Logout200ResponseFromJSON(jsonValue));
+        });
+    }
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
      */
-    apiV1AuthSessionGet(initOverrides) {
+    logout(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.apiV1AuthSessionGetRaw(initOverrides);
+            const response = yield this.logoutRaw(initOverrides);
             return yield response.value();
         });
     }
@@ -154,7 +185,7 @@ export class V1AuthApi extends runtime.BaseAPI {
      * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
      * Check authentication status
      */
-    apiV1AuthWhoamiGetRaw(initOverrides) {
+    whoAmIRaw(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
             const queryParameters = {};
             const headerParameters = {};
@@ -168,16 +199,16 @@ export class V1AuthApi extends runtime.BaseAPI {
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => ApiV1AuthWhoamiGet200ResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => WhoAmI200ResponseFromJSON(jsonValue));
         });
     }
     /**
      * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
      * Check authentication status
      */
-    apiV1AuthWhoamiGet(initOverrides) {
+    whoAmI(initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.apiV1AuthWhoamiGetRaw(initOverrides);
+            const response = yield this.whoAmIRaw(initOverrides);
             return yield response.value();
         });
     }

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

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

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

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

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

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