mudbase 1.3.12 → 1.3.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6b5e13592dccde7ef909b28d613ea96af98ea0c2f600730cb11e03ca87a51a47
-  data.tar.gz: 62210483d27da3f87cea9d1bbf78cedb37f9547f00442634483239da74e5ded3
+  metadata.gz: 38e4e555506ffd0d5eacf39b907fdde8a756218cbe704be137d07f06a421856e
+  data.tar.gz: 33a01e5a5fcdc88487ec2a5c1f15bcc387216883de62e03ae5b48144b42c2fe5
 SHA512:
-  metadata.gz: 43d036e14110ed9113dad36b6d20c4d5d02dca272b051a31530168dd0cb0530fa29e6685d94eec9c5a956950e34f24786688aa0f94a49a0844a925041a0dc698
-  data.tar.gz: ecf01547710d93574d7145d4695fe52e7d8df4996afd4c8dc1c721a01400e6d9db3a153ca348a2e8c20742e6e0ee024ef5a91c44c5709679d248c8381ec57023
+  metadata.gz: f3c245b7d02329def094bc9938c6d37d47caec13e6bcb992224d4a85c3b73746dbce2eff22e51a2c1018f38039d034ef1ba18a7050e3db4893172194b277a34b
+  data.tar.gz: f92bacc912701b20adc04040c05a8b0d54a41bce0987d3fedc835a06eb883ed286afc12b21f95b6b6736ce282f6d74a7dfdfe85fc2a3f59c12a72900346110f7

data/README.md

@@ -1,7 +1,6 @@
-# MUDBASE ruby SDK
+# MUDBASE Ruby SDK
 
-Official **ruby** client for the [MUDBASE](https://mudbase.dev) platform.  
-Packages are versioned from our OpenAPI spec so they stay in sync with the API.
+Mudbase is a backend platform: authentication, a schema-driven database, file storage, serverless functions, webhooks, and real-time and transactional messaging behind one API. The Ruby SDK is a native Ruby client for that API, so you can manage users and organizations, define collections and query data, store and serve files, invoke functions, and configure webhooks without hand-rolling HTTP requests.
 
 ## Installation
 
@@ -9,9 +8,31 @@ Packages are versioned from our OpenAPI spec so they stay in sync with the API.
 gem install mudbase
 ```
 
-## Usage
+## Quickstart
 
-See [API documentation](https://docs.mudbase.dev/api) and generated source for endpoint-level examples.
+```ruby
+require "mudbase"
+
+Mudbase.configure do |config|
+  config.host = "cloud.mudbase.dev"
+  config.api_key["ApiKeyAuth"] = "YOUR_API_KEY"
+end
+
+collections = Mudbase::CollectionsApi.new
+result = collections.list_collections("YOUR_PROJECT_ID")
+puts result.collections
+```
+
+## What you can do
+
+- **Authentication** - sign-up, sign-in, sessions, and API key management
+- **Database** - schema-defined collections with typed CRUD and filtered queries
+- **Storage** - buckets and file uploads and downloads
+- **Realtime** - WebSocket events and live data subscriptions
+- **Functions** - deploy and invoke serverless functions
+- **Messaging** - transactional email, SMS, and push notifications
+- **Webhooks** - configurable delivery with retry and logs
+- **Roles & permissions** - project-level access control
 
 ## Documentation
 
@@ -20,4 +41,4 @@ See [API documentation](https://docs.mudbase.dev/api) and generated source for e
 
 ## Support
 
-Issues for this mirror repo: https://docs.mudbase.dev
+Questions or issues: open one at https://github.com/themudhaxk/mudbase-sdk-ruby, or reach us at support@mudbase.dev.

data/docs/OrgDomainEntryWithDns.md

@@ -20,9 +20,9 @@
 | **platform_activation_pending** | **Boolean** | True while Mudbase TXT passed but custom host not yet active (includes CNAME and platform DNS pipeline). | [optional] |
 | **custom_domain_live_for_api_traffic** | **Boolean** |  | [optional] |
 | **custom_domain_verification_step** | **Integer** | Console wizard step 1–3; null when active/verified. | [optional] |
-| **routing_cname_target** | **String** | Routing CNAME target: Fly Certificates API `dns_requirements.cname` when Fly ACME has provisioned and stored requirements; otherwise fallback from env `CUSTOM_DOMAIN_API_CNAME_TARGET`. | [optional] |
-| **dns_records** | [**Array<OrgDnsRecord>**](OrgDnsRecord.md) | Unified checklist: Mudbase ownership TXT, routing CNAME from Fly `dns_requirements.cname` (purpose `routing`) when provisioned else env fallback, and Fly rows (`fly_ownership`, `acme_challenge`, …) when Fly ACME is enabled and the certificate has been provisioned after Mudbase TXT. Empty or absent when Fly ACME is off or not yet provisioned. Prefer this over `platformDnsVerification` alone for org-facing DNS UI. | [optional] |
-| **fly_certificate_status** | **String** | Fly Certificates API `status` when **`CUSTOM_DOMAIN_FLY_ACME_ENABLED`** and token/app are configured (e.g. `pending_validation`, `active`). Null when Fly ACME is not in use for this deployment. | [optional] |
+| **routing_cname_target** | **String** | Routing CNAME target: the managed certificate's provisioned CNAME target when requirements have been stored; otherwise the platform default target. | [optional] |
+| **dns_records** | [**Array<OrgDnsRecord>**](OrgDnsRecord.md) | Unified checklist: Mudbase ownership TXT, routing CNAME (purpose `routing`) when provisioned else the platform default, and the managed certificate-provisioning rows once the managed certificate has been provisioned after the Mudbase TXT. Empty or absent when the certificate is not yet provisioned. Prefer this over `platformDnsVerification` alone for org-facing DNS UI. | [optional] |
+| **fly_certificate_status** | **String** | Managed certificate `status` during provisioning (e.g. `pending_validation`, `active`). Null when managed certificate provisioning is not in use for this deployment. | [optional] |
 | **platform_dns_verification** | [**OrgPlatformDnsVerificationCustomer**](OrgPlatformDnsVerificationCustomer.md) |  | [optional] |
 | **cname_submitted_at** | **Time** |  | [optional] |
 | **cname_approved_at** | **Time** |  | [optional] |

data/docs/OrgVerifyCustomDomainDnsSuccessResponse.md

@@ -13,12 +13,12 @@
 | **dns_txt_host** | **String** |  |  |
 | **dns_txt_value** | **String** |  |  |
 | **edge** | [**OrgEdgeHints**](OrgEdgeHints.md) |  | [optional] |
-| **dns_records** | [**Array<OrgDnsRecord>**](OrgDnsRecord.md) | Same shape as `OrgDomainEntryWithDns.dnsRecords` when Fly ACME ran after this successful verify; omit or empty when Fly ACME is disabled or not provisioned. | [optional] |
-| **fly_certificate_status** | **String** | Fly certificate status after verify when Fly ACME is active; null otherwise | [optional] |
-| **fly_acme_enabled** | **Boolean** | True when Fly ACME would call the Certificates API (token, app, CUSTOM_DOMAIN_FLY_ACME_ENABLED). | [optional] |
-| **fly_acme_disabled_reason** | **String** | When `flyAcmeEnabled` is false, why Fly ACME did not run (ops misconfiguration hint). | [optional] |
-| **fly_provision_error** | **String** | When Fly ACME is enabled but POST acme failed, Fly API error message for support; null on success. | [optional] |
-| **fly_legacy_staff_pipeline** | **Boolean** | When true, `CUSTOM_DOMAIN_FLY_LEGACY_STAFF_PIPELINE` is on — status may stay `cname_pending_staff` and staff approve-cname is required even if Fly provision succeeds. | [optional] |
+| **dns_records** | [**Array<OrgDnsRecord>**](OrgDnsRecord.md) | Same shape as `OrgDomainEntryWithDns.dnsRecords` when certificate provisioning ran after this successful verify; omit or empty when provisioning is disabled or not yet run. | [optional] |
+| **fly_certificate_status** | **String** | Managed certificate status after verify when provisioning is active; null otherwise | [optional] |
+| **fly_acme_enabled** | **Boolean** | True when automated managed-certificate provisioning is configured for this deployment. | [optional] |
+| **fly_acme_disabled_reason** | **String** | When `flyAcmeEnabled` is false, why automated provisioning did not run (ops misconfiguration hint). | [optional] |
+| **fly_provision_error** | **String** | When provisioning is enabled but certificate issuance failed, the provider error message for support; null on success. | [optional] |
+| **fly_legacy_staff_pipeline** | **Boolean** | When true, the legacy staff pipeline is on: status may stay `cname_pending_staff` and staff approve-cname is required even if certificate provisioning succeeds. | [optional] |
 
 ## Example
 

data/docs/OrganizationsApi.md

@@ -28,7 +28,7 @@ All URIs are relative to *https://cloud.mudbase.dev*
 | [**org_custom_domain_platform_ready**](OrganizationsApi.md#org_custom_domain_platform_ready) | **POST** /api/orgs/{orgId}/projects/{projectId}/domains/{hostname}/platform-ready | Notify platform ops that hosting or edge work is ready (email) |
 | [**org_custom_domain_submit_cname**](OrganizationsApi.md#org_custom_domain_submit_cname) | **POST** /api/orgs/{orgId}/projects/{projectId}/domains/{hostname}/submit-cname | Custom domain step 2 (optional): org confirms routing CNAME was added |
 | [**org_custom_domain_submit_platform_dns_verification_deprecated**](OrganizationsApi.md#org_custom_domain_submit_platform_dns_verification_deprecated) | **POST** /api/orgs/{orgId}/projects/{projectId}/domains/{hostname}/submit-platform-dns-verification | Deprecated — use POST .../verify-platform-dns |
-| [**org_custom_domain_verify_platform_dns**](OrganizationsApi.md#org_custom_domain_verify_platform_dns) | **POST** /api/orgs/{orgId}/projects/{projectId}/domains/{hostname}/verify-platform-dns | Custom domain step 3: verify platform DNS (manual TXT or Fly certificate readiness) |
+| [**org_custom_domain_verify_platform_dns**](OrganizationsApi.md#org_custom_domain_verify_platform_dns) | **POST** /api/orgs/{orgId}/projects/{projectId}/domains/{hostname}/verify-platform-dns | Custom domain step 3: verify platform DNS (manual TXT or managed certificate readiness) |
 | [**patch_org_custom_domain**](OrganizationsApi.md#patch_org_custom_domain) | **PATCH** /api/orgs/{orgId}/projects/{projectId}/domains/{hostname} | Update domain status or regenerate verification token |
 | [**remove_sub_organization_member**](OrganizationsApi.md#remove_sub_organization_member) | **DELETE** /api/orgs/{orgId}/suborgs/{suborgId}/members/{userId} | ~~Remove member from sub-organization~~ (deprecated) |
 | [**remove_team_member**](OrganizationsApi.md#remove_team_member) | **DELETE** /api/orgs/{orgId}/members/{userId} | Remove team member from organization |
@@ -48,7 +48,7 @@ All URIs are relative to *https://cloud.mudbase.dev*
 
 Add a custom domain
 
-Creates a pending domain row; the response **`domain`** uses the compact **`OrgDomainEntryOrgConsole`** shape (**`dnsRecords`** includes the Mudbase ownership TXT). **`dnsRecords`** may include Mudbase TXT and routing CNAME only until Mudbase TXT succeeds and Fly ACME (if enabled) provisions a certificate. **`flyCertificateStatus`** is typically omitted until Fly ACME runs after first successful **`verify-dns`**. 
+Creates a pending domain row; the response **`domain`** uses the compact **`OrgDomainEntryOrgConsole`** shape (**`dnsRecords`** includes the Mudbase ownership TXT). **`dnsRecords`** may include the Mudbase TXT and routing CNAME only until the Mudbase TXT succeeds and the managed certificate is provisioned. **`flyCertificateStatus`** is typically omitted until certificate provisioning runs after the first successful **`verify-dns`**. 
 
 ### Examples
 
@@ -403,7 +403,7 @@ end
 
 Get DNS TXT record instructions for one hostname
 
-Returns the same shape as list/add for one hostname (URL-encode `hostname` in the path), including **`dnsRecords`** and **`flyCertificateStatus`** when applicable. See **`listOrgCustomDomains`** for how Fly ACME and Cloudflare SaaS affect those fields. 
+Returns the same shape as list/add for one hostname (URL-encode `hostname` in the path), including **`dnsRecords`** and **`flyCertificateStatus`** when applicable. See **`listOrgCustomDomains`** for how managed certificate provisioning affects those fields. 
 
 ### Examples
 
@@ -1039,7 +1039,7 @@ nil (empty response body)
 
 Custom domain background sweep status (internal)
 
-Returns the last automated custom-domain sweep (TXT recheck + Fly ACME retry), job env flags, and Fly deploy troubleshooting hints when the proxy reports the app is not listening on 0.0.0.0:PORT. Requires header `X-Internal-Api-Key` (same as other /internal routes).
+Returns the last automated custom-domain sweep (TXT recheck + certificate provisioning retry), job env flags, and deploy troubleshooting hints when the proxy reports the app is not listening on 0.0.0.0:PORT. Requires header `X-Internal-Api-Key` (same as other /internal routes).
 
 ### Examples
 
@@ -1392,7 +1392,7 @@ end
 
 List custom domains and DNS verification hints
 
-Returns allowed hostnames for **this project**, primary hostname (per project), API base URL, and per-domain DNS guidance.  Each row uses **`dnsRecords`** for the Mudbase ownership TXT (purpose **`mudbase_ownership`**) and routing **CNAME** from Fly **`dns_requirements.cname`** when Fly ACME has provisioned (else fallback **`CUSTOM_DOMAIN_API_CNAME_TARGET`**), and—when Fly ACME is enabled (**`FLY_API_TOKEN`** + **`CUSTOM_DOMAIN_FLY_ACME_ENABLED`**)—Fly rows (`fly_ownership`, `acme_challenge`, etc.) after the org has passed Mudbase TXT at least once. **`flyCertificateStatus`** mirrors Fly’s certificate state when ACME automation is on (e.g. `pending_validation`, `active`).  **`edge`** appears only when edge SSL (SSL-for-SaaS) is configured. Fly ACME and edge SSL are mutually exclusive on the server.  Requires Growth, Scale, or Enterprise plan (custom domains included in plan features). 
+Returns allowed hostnames for **this project**, primary hostname (per project), API base URL, and per-domain DNS guidance.  Each row uses **`dnsRecords`** for the Mudbase ownership TXT (purpose **`mudbase_ownership`**) and the routing **CNAME** target that Mudbase provisions for the hostname (else the platform default target). Once the ownership TXT has passed at least once, Mudbase provisions and manages the TLS certificate for the hostname automatically and may add further checklist rows (for example `acme_challenge`) needed to complete certificate issuance. The certificate status field mirrors the managed certificate’s state during issuance (e.g. `pending_validation`, `active`).  Managed edge TLS details are present only on deployments that serve managed edge certificates.  Requires Growth, Scale, or Enterprise plan (custom domains included in plan features). 
 
 ### Examples
 
@@ -1605,7 +1605,7 @@ nil (empty response body)
 
 Custom domain step 2 (optional): org confirms routing CNAME was added
 
-Usually unnecessary. With Fly ACME default automation, Mudbase TXT verify may already set `cname_approved`. Legacy pipelines may queue `cname_pending_staff` until staff **`approve-cname`**. Use **`routingCnameTarget`** from **`GET .../projects/{projectId}/domains`** (Fly **`dns_requirements.cname`** when provisioned, else **`CUSTOM_DOMAIN_API_CNAME_TARGET`**). 
+Usually unnecessary. With automated certificate provisioning, the Mudbase TXT verify may already set `cname_approved`. Legacy pipelines may queue `cname_pending_staff` until staff **`approve-cname`**. Use **`routingCnameTarget`** from **`GET .../projects/{projectId}/domains`** (the managed routing CNAME target when provisioned, else the platform default target). 
 
 ### Examples
 
@@ -1678,7 +1678,7 @@ end
 
 Deprecated — use POST .../verify-platform-dns
 
-Deprecated alias of **`orgCustomDomainVerifyPlatformDns`** (same behavior — manual TXT and/or Fly ACME path per server config).
+Deprecated alias of **`orgCustomDomainVerifyPlatformDns`** (same behavior: manual TXT and/or automated certificate provisioning per deployment).
 
 ### Examples
 
@@ -1749,9 +1749,9 @@ end
 
 > <OrgPatchDomainResponse> org_custom_domain_verify_platform_dns(org_id, project_id, hostname)
 
-Custom domain step 3: verify platform DNS (manual TXT or Fly certificate readiness)
+Custom domain step 3: verify platform DNS (manual TXT or managed certificate readiness)
 
-**Manual path (no Fly ACME):** After staff **`PATCH .../platform-dns-verification`**, the org adds the published TXT and calls this endpoint. The API resolves public TXT at **`platformDnsVerification.recordName`** and matches **`recordValue`**. On success, `status` → **`platform_dns_pending_review`** until staff **`POST .../activate`**.  **Fly ACME path (default):** When Fly ACME is enabled and **`CUSTOM_DOMAIN_FLY_LEGACY_STAFF_PIPELINE`** is **not** set, the org calls this after Mudbase TXT and Fly DNS rows are in place (status typically **`cname_approved`** from automated verify-dns). The API triggers Fly **`POST .../check`** and **`GET`** certificate with bounded retries. On success, `status` → **`active`** and the org may receive the activation email—**no** staff **`approve-cname`** or **`activate`** required.  **Fly legacy:** If **`CUSTOM_DOMAIN_FLY_LEGACY_STAFF_PIPELINE=true`**, behavior matches the older flow: staff **`approve-cname`** may be required first; after a ready Fly cert, **`status`** becomes **`active`** only when **`CUSTOM_DOMAIN_FLY_AUTO_ACTIVATE=true`**, else **`platform_dns_pending_review`** until staff **`activate`**.  **`platform_dns_verification_failed`** may include **`details.flyStatus`** / **`details.flyError`** on the Fly path. 
+**Manual path:** After staff **`PATCH .../platform-dns-verification`**, the org adds the published TXT and calls this endpoint. The API resolves public TXT at **`platformDnsVerification.recordName`** and matches **`recordValue`**. On success, `status` → **`platform_dns_pending_review`** until staff **`POST .../activate`**.  **Automated path (default):** When automated certificate provisioning is in effect, the org calls this after the Mudbase TXT and the certificate DNS rows are in place (status typically **`cname_approved`** from automated verify-dns). The API checks the managed certificate with bounded retries. On success, `status` → **`active`** and the org may receive the activation email, with no staff **`approve-cname`** or **`activate`** required.  **Legacy path:** In the legacy staff pipeline, staff **`approve-cname`** may be required first; after the managed certificate is ready, **`status`** becomes **`active`** on auto-activation, else **`platform_dns_pending_review`** until staff **`activate`**.  **`platform_dns_verification_failed`** may include **`details.flyStatus`** / **`details.flyError`** with provisioning error context. 
 
 ### Examples
 
@@ -1770,7 +1770,7 @@ project_id = 'project_id_example' # String |
 hostname = 'hostname_example' # String | 
 
 begin
-  # Custom domain step 3: verify platform DNS (manual TXT or Fly certificate readiness)
+  # Custom domain step 3: verify platform DNS (manual TXT or managed certificate readiness)
   result = api_instance.org_custom_domain_verify_platform_dns(org_id, project_id, hostname)
   p result
 rescue Mudbase::ApiError => e
@@ -1786,7 +1786,7 @@ This returns an Array which contains the response data, status code and headers.
 
 ```ruby
 begin
-  # Custom domain step 3: verify platform DNS (manual TXT or Fly certificate readiness)
+  # Custom domain step 3: verify platform DNS (manual TXT or managed certificate readiness)
   data, status_code, headers = api_instance.org_custom_domain_verify_platform_dns_with_http_info(org_id, project_id, hostname)
   p status_code # => 2xx
   p headers # => { ... }
@@ -2558,7 +2558,7 @@ end
 
 Verify domain ownership via DNS TXT
 
-Looks up TXT at `_mudbase-verify.<hostname>` for value `mudbase-domain-verification=<token>`.  When the server has **`CLOUDFLARE_API_TOKEN`** and **`CLOUDFLARE_ZONE_ID`** configured (and Fly ACME is **not** enabled), a successful verify also creates or refreshes a Cloudflare Custom Hostname (SSL for SaaS) and returns **`cloudflare`** with DCV hints.  When **Fly ACME** is enabled (**`FLY_API_TOKEN`** + **`CUSTOM_DOMAIN_FLY_ACME_ENABLED=true`** + app slug), a successful verify calls Fly’s Certificates API (`POST .../certificates/acme`) and persists DNS requirements. If Fly returns DNS rows and **`CUSTOM_DOMAIN_FLY_LEGACY_STAFF_PIPELINE`** is **not** set, status advances to **`cname_approved`** in the same response (no staff **`approve-cname`**); **`org.domain.cname_staff_queued`** is not logged for that path. Otherwise (legacy Fly or non-Fly), first success from `pending`/`failed` may move to **`cname_pending_staff`** and queue staff as before.  The **200** response may include **`dnsRecords`**, **`flyCertificateStatus`**, and **`routingCnameTarget`** from Fly’s **`dns_requirements.cname`** when provisioned.  Cloudflare SaaS and Fly ACME cannot both be enabled; the API process refuses to start if both are configured. 
+Looks up TXT at `_mudbase-verify.<hostname>` for value `mudbase-domain-verification=<token>`.  On a successful verify, Mudbase begins provisioning and managing the TLS certificate for the hostname automatically. Depending on the deployment, the response may include managed edge TLS details with domain-control validation (DCV) hints for the certificate.  When automated certificate provisioning is in effect, a successful verify records the certificate’s DNS requirements and status may advance to **`cname_approved`** in the same response (no staff **`approve-cname`** step). Otherwise, first success from `pending`/`failed` may move to **`cname_pending_staff`** and queue platform review as before.  The **200** response may include **`dnsRecords`**, certificate status, and **`routingCnameTarget`** for the managed certificate once its requirements are provisioned. 
 
 ### Examples
 

data/docs/SimulateAppPermissionsRequest.md

@@ -21,7 +21,7 @@ instance = Mudbase::SimulateAppPermissionsRequest.new(
   role_slug: null,
   operation_id: sendEmail,
   method: POST,
-  pathname: /api/messaging/projects/685ad30be129932fbb7a1047/messaging/email,
+  pathname: /api/messaging/projects/65f1a2b3c4d5e6f7a8b9c0d1/messaging/email,
   path: null
 )
 ```

data/lib/mudbase/api/add_ons_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/api_keys_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/authentication_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/backups_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/billing_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/buckets_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/chat_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/collections_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/compliance_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/data_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/email_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/files_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/functions_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/health_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/integrations_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/kyc_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/mcp_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/messaging_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/monitoring_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/multi_role_feature_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: fiat only for project subscriptions and org BaaS checkout (platform fee split). On-chain billing is not exposed on these APIs (optional `crypto-payment-module/` in repo, not mounted by default). - 🏢 Enterprise / Phase 4: custom domains on Growth, Scale, and Enterprise (TXT DNS at `_mudbase-verify.<hostname>`); `settings.customDomainAddon` is optional (billing/legacy); dedicated DB migration script, periodic DNS recheck job, optional `infrastructureEnvironments[]` and edge/metering fields on `dedicated`. 
 
-The version of the OpenAPI document: 1.3.12
+The version of the OpenAPI document: 1.3.13
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0