Add Maia Resources doc

content/en/docs/control-center/maia-resources.md

@@ -0,0 +1,77 @@
+---
+title: "Maia Resources"
+url: /control-center/maia-resources/
+description: "Describes how to provision and deprovision Maia Resources using self-service."
+weight: 25
+---
+
+## Introduction
+
+Maia Resources is your access point to increase the capacity of Maia Units for using Maia Make in Studio Pro. It allows admins to provision, upgrade, downgrade, and deprovision Maia Units and manage the resources for Maia Make for their company. For more information on Maia Make’s capabilities, refer to [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/).
+
+## Prerequisites
+
+1. Sufficient token entitlements – The user should have an adequate number of available Mendix Cloud Tokens to allocate for Maia Unit provisioning.
+2. Valid subscription plan – The user's Mendix subscription must be based on the FY21 price list or newer. Older subscription plans are not eligible for provisioning.
+3. Single account ownership – The user must have a single account. Owning multiple accounts is not supported for Maia Unit provisioning.
+4. Enterprise platform subscription – The user must have a single active enterprise platform subscription.
+
+## Overview of Maia Units
+
+The overview page provides a centralized view of all Maia Units currently provisioned for your company.
+
+* Type – The type or resources; either Free or Provisioned
+* Cloud Tokens – The number of Cloud Tokens used
+* Capacity (Maia Units) – The number of Maia Units per month your organization can use
+* State – Whether the resources is active, or ready to be downgraded or deprovisioned
+
+{{< figure src="/attachments/control-center/maia-resources/overview.jpeg" alt="" >}}
+
+## Increasing Your Maia Units Capacity {#increase-maia-units}
+
+1. **Make sure you have Cloud Tokens available**
+Cloud Tokens are purchased through your Mendix subscription. If your organization already has Cloud Tokens allocated to other services, you can reassign them. Check your available balance in the Control Center. If you need to purchase more, contact your Mendix account manager.
+2. **Convert Cloud Tokens to Maia Units**
+In the Control Center, go to Maia Resources and select Provision Resource. Choose how many Cloud Tokens to allocate. Each Cloud Token gives you 100 Maia Units per month.
+3. **Use Maia in Studio Pro**
+Your new capacity is active immediately. Studio Pro unblocks and Maia Make becomes available again.
+
+### Key Considerations
+
+* Monthly cycle – Your Maia Units reset each month. Unused units do not roll over.
+* Upgrades – Upgrades take effect immediately. Downgrades and cancellations take effect at the end of the current month; you keep access until then.
+* Free allowance – Every Mendix account includes a base allocation each month before any Cloud Tokens are needed.
+
+## Provisioning Maia Units {#provisioning-maia-units}
+
+You can provision any Maia resources directly within the Control Center using the self-service capability. To do this, select **Provision Resource**. 
+
+This allows you to select how many Cloud Token to use to provision Maia Units. Every Cloud Token provisions 100 Maia Units per month.
+
+{{< figure src="/attachments/control-center/maia-resources/provision.jpeg" alt="" >}}
+
+Click **Provision** to select an amount of cloud tokens. An pop-up shows the Maia Units capacity that will be added. Clicking **Provision** again completes the process. You are taken back to the **Maia Resource** page where the newly provisioned Maia Units appear in the list.
+
+{{< figure src="/attachments/control-center/maia-resources/resource-summary.jpeg" alt="" width="300" >}}
+
+## Upgrading Maia Units {#upgrading-maia-units}
+
+To upgrade your provisioned Maia Units, select a plan of type **Provisioned** from your resources overview and click **Edit Resource**. This opens the page of your current resource, showing the amount of allotted Cloud Tokens. Increase the amount of Cloud Tokens to upgrade your provisioned Maia Units, then click **Save Changes**. Upgrades will take effect immediately.
+
+{{< figure src="/attachments/control-center/maia-resources/upgrade.jpeg" alt="" >}}
+
+## Downgrading Maia Units {#downgrading-maia-units}
+
+To downgrade your amount of provisioned Maia Units, select a plan of type **Provisioned** from your resources overview and press **Edit Resource**. This opens the page for your current resource, showing the amount of allotted Cloud Tokens. Decrease the amount of Cloud Tokens to downgrade your provisioned Maia Units, then click **Save Changes** to confirm.
+
+{{% alert color="info" %}}
+Your subscription plan operates on a monthly bundle cycle. When you downgrade, the new plan takes effect at the start of the new month. Until that date, you can still use the resource, and the status in the overview reads **Plan Downgrade Scheduled**.
+{{% /alert %}}
+
+## Deprovisioning Maia Units {#deprovisioning-maia-units}
+
+To deprovision, select a plan of type **Provisioned** from your resources overview and click **Deprovision**. A confirmation pop-up window appears. Click **Deprovision** to confirm.
+
+{{% alert color="info" %}}
+Your subscription plan operates on a monthly bundle cycle. When you deprovision a resource, the deprovisioning takes effect at the end of the current subscription month. Until that date, you can still use the resource and status in the overview reads **Plan Deprovision Scheduled**.
+{{% /alert %}}

content/en/docs/refguide/mendix-ai-assistance/_index.md

@@ -25,12 +25,16 @@ For information on what third-party services Maia uses and what data are sent to
 
 For more information on how to ensure optimal performance of Maia, see the [Best Practice for Maia Performance](#maia-performance-best-practice) section below.
 
-## Fair Use Policy {#fair-use}
+## Maia Usage Limits {#maia-usage}
 
-Mendix applies fair use limits to maintain a reliable experience for all users. If usage exceeds these limits, your Maia access may be temporarily paused. Account access is reviewed on a weekly schedule. Your account will be automatically reactivated within seven days once the review period concludes.
+To ensure a reliable experience with Maia, Mendix provides two ways to manage your usage: purchasing Maia Units and configuring a custom AI provider of your choice. Every user receives 200 free units per month and can purchase more as needed.
+
+When your free Maia Units allocation or purchased Maia Units have been consumed, you receive a notification in Studio Pro indicating that you need to take action before you can use Maia Make again. Your allocation resets at the start of each month. To increase your capacity, you can purchase additional Maia Units. For more information on purchasing Maia Units, see [Increasing Your Maia Usage Capacity](/control-center/maia-resources/#increase-maia-units). 
 
 If you need uninterrupted access to Maia capabilities, you can [configure a custom AI provider](/refguide/maia-make/#custom-provider) to use your own LLM provider.
 
+Alternatively, you can use the Studio Pro MCP Server's bring your own agent (BYO Agent) capabilities, which allows you to use Maia's capabilities directly from external clients, including AI coding assistants, agents, and other MCP-based LLM tools. For more information on the Studio Pro MCP Server, see [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/).
+
 ## Network Configuration Requirements {#maia-network-requirement}
 
 To ensure the smooth operation of Mendix AI Assistance (Maia), the following network requirements must be met:

content/en/docs/releasenotes/studio-pro/11/11.12.md

@@ -28,37 +28,38 @@ For existing apps, Studio Pro automatically assigns a **Module ID** to every mod
 The **Module ID** and **checksum** are stored in a new *manifest.json* file inside the module package, alongside the existing *package.xml* for backward compatibility. For more information, see [Module Settings](/refguide/module-settings/#package).
 
 #### Other New Features
-
-* We introduced a modernized **Variables** pane. It now preserves expanded nodes as you step through the debugger, so you no longer lose your place between steps.
-* We improved offline synchronization error handling so that when the server rejects uploaded objects (for example, due to validation rules or security constraints), the synchronization action now throws a `PartialSynchronizationError` (as long as **Throw error when server rejects objects during synchronization** option is enabled). Nanoflow developers can catch this error in a try/catch block to present a message to the user or take corrective action.
-* Toggling the web fetch tool in Maia preferences now takes effect immediately, without needing to relaunch Studio Pro.
-* We added the ability for the user to see the current Studio Pro version through the Preferences API.
-* We added a `documentAdded` event to the `IProjectChangesApi`, allowing extensions to react when a new document is added to the project.
-* We added the ability to filter the comparison pane by change status (such as added, modified, deleted, or moved). Filters are persisted across sessions, and an indicator is shown when any filter differs from the default.
-* We added sortable columns to the **Comparison** pane. You can now click any column header in the **Documents** or **Elements** views to sort the list, making it easier to find and group changes.
-* We implemented a new function `DATEFORMAT` in OQL. For more details, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateformat-function).
-* We implemented two new functions in OQL: `RPAD` and `LPAD`. For more details, see the documentation for [LPAD](/refguide/oql-expression-syntax/#lpad-function) and [RPAD](/refguide/oql-expression-syntax/#rpad-function).
-* You can now use Maia to work with theming and styling in Studio Pro. Maia can modify theme variables, create custom styling, and manage design properties—for example, updating colors, spacing, and typography across your app based on your styling requirements.
-* Maia can now ask you clarifying questions before proceeding. When Maia needs more information, it will present one or more questions directly in the chat—supporting open-ended, single choice, and multiple choice answers—and use your responses to continue with the right approach.
-* We released the Embedded Client in public Beta. You can now embed your Mendix app into any host application by configuring an [Embedded Navigation Profile](/refguide/navigation/#embedded) and following the instructions in the [Embedding the Client](/refguide/mendix-client/embedding-the-client/) guide.
-* We added a `permissionsChanged` event to the Extension Permissions API, allowing extensions to be notified when permission states change.
-* You can now add custom instructions on either project or module level. Project-level instructions will be added to every Maia conversation, while module-level ones will be added whenever Maia works with documents of a given module.
-* Maia now thinks before responding. You can see what it is considering in real time, and revisit its reasoning at any point during the conversation.
-* MCP OAuth authentication now uses a dedicated callback server on a fixed port range (44380–44384), enabling use with MCP servers that require pre-registered redirect URIs.
-* MCP connections now support Mendix Identity (MxId3) authentication. MCP servers hosted on *.mendix.com automatically receive the user's platform access token.
-* You can now add Maia Agent Instructions. Maia Instructions are agent instructions that are automatically added to the conversation context. You can add them to the project or module level. For more information, see [Maia Agent Instructions (AGENTS.md)](/refguide/maia-instructions/).
-* We introduced the following new features to skills in Maia:
-    * A new **Skills** pane in Maia shows all custom skills that are currently loaded, their status, and which module they belong to (for module-level skills). You can filter the list to show only skills with errors. To apply the updated skills immediately, you can sync the skills. For more information, see [Skill Overview](/refguide/maia-agent-skills/#skill-overview) section in Maia Agent Skills.
-    * You can now add custom skills to non-protected app modules. These skills are exported together with other contents of the module.
-    * Maia now shows which custom skill (or which resource within a skill) it is drawing on while working, so you can follow along as it applies your project's conventions.
-* We released a feature in public beta that lets you configure a custom LLM provider. In addition to the default Mendix Platform provider, you can now configure OpenAI-compatible providers or AWS Bedrock on a per-project basis. Mendix still recommends using the Mendix Platform provider for the best experience. For more information, see [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider).
-* Maia is now better at fetching and understanding content from web pages by focusing on the main content.
-* You can now attach Markdown files (*.md*, *.mdx*) to your Maia chat messages. Each file can be up to 50 KB, and you can attach as many as you need. The file contents are sent to Maia as context alongside your prompt.
-* Maia Agent session can be saved by navigating **Help** > **Support Tools** > **Capture Maia Agent Session**, making it easier to share session details when troubleshooting or reporting issues.
-* Data Transformers are now generally available. This allows you to transform complex JSON data, including cases that were never supported before.
-    * You can use a Data Transformer as a preprocessing step before passing the data into an Import Mapping, or use the transformed JSON directly, for example to send data to another system.
-    * Maia support has been added, so Maia can help creating and modifying Data Transformers.
-    * For more information, see [Data Transformer](/refguide/data-transformers/).
+
+- We introduced an option to purchase Maia Units. This resource allows you add additional capacity for your company to use Maia Make. For more information, see [Maia Resources](/control-center/maia-resources/).   
+- We introduced a modernized **Variables** pane. It now preserves expanded nodes as you step through the debugger, so you no longer lose your place between steps.
+- We improved offline synchronization error handling so that when the server rejects uploaded objects (for example, due to validation rules or security constraints), the synchronization action now throws a `PartialSynchronizationError` (as long as **Throw error when server rejects objects during synchronization** option is enabled). Nanoflow developers can catch this error in a try/catch block to present a message to the user or take corrective action.
+- Toggling the web fetch tool in Maia preferences now takes effect immediately, without needing to relaunch Studio Pro.
+- We added the ability for the user to see the current Studio Pro version through the Preferences API.
+- We added a `documentAdded` event to the `IProjectChangesApi`, allowing extensions to react when a new document is added to the project.
+- We added the ability to filter the comparison pane by change status (such as added, modified, deleted, or moved). Filters are persisted across sessions, and an indicator is shown when any filter differs from the default.
+- We added sortable columns to the **Comparison** pane. You can now click any column header in the **Documents** or **Elements** views to sort the list, making it easier to find and group changes.
+-  We implemented a new function `DATEFORMAT` in OQL. For more details, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateformat-function).
+- We implemented two new functions in OQL: `RPAD` and `LPAD`. For more details, see the documentation for [LPAD](/refguide/oql-expression-syntax/#lpad-function) and [RPAD](/refguide/oql-expression-syntax/#rpad-function).
+- You can now use Maia to work with theming and styling in Studio Pro. Maia can modify theme variables, create custom styling, and manage design properties—for example, updating colors, spacing, and typography across your app based on your styling requirements.
+- Maia can now ask you clarifying questions before proceeding. When Maia needs more information, it will present one or more questions directly in the chat—supporting open-ended, single choice, and multiple choice answers—and use your responses to continue with the right approach.
+- We released the Embedded Client in public Beta. You can now embed your Mendix app into any host application by configuring an [Embedded Navigation Profile](/refguide/navigation/#Embedded) and following the instructions in the [Embedding the Client](/refguide/mendix-client/embedding-the-client/) guide.
+- We added a `permissionsChanged` event to the Extension Permissions API, allowing extensions to be notified when permission states change.
+- You can now add custom instructions on either project or module level. Project-level instructions will be added to every Maia conversation, while module-level ones will be added whenever Maia works with documents of a given module.
+- Maia now thinks before responding. You can see what it is considering in real time, and revisit its reasoning at any point during the conversation.
+- MCP OAuth authentication now uses a dedicated callback server on a fixed port range (44380–44384), enabling use with MCP servers that require pre-registered redirect URIs.
+- MCP connections now support Mendix Identity (MxId3) authentication. MCP servers hosted on *.mendix.com automatically receive the user's platform access token.
+- You can now add Maia Agent Instructions. Maia Instructions are agent instructions that are automatically added to the conversation context. You can add them to the project or module level. For more information, see [Maia Agent Instructions (AGENTS.md)](/refguide/maia-instructions/).
+- We introduced the following new features to skills in Maia:
+    - A new **Skills** pane in Maia shows all custom skills that are currently loaded, their status, and which module they belong to (for module-level skills). You can filter the list to show only skills with errors. To apply the updated skills immediately, you can sync the skills. For more information, see [Skill Overview](/refguide/maia-agent-skills/#skill-overview/) section in Maia Agent Skills.
+    - You can now add custom skills to non-protected app modules. These skills are exported together with other contents of the module.
+    - Maia now shows which custom skill (or which resource within a skill) it is drawing on while working, so you can follow along as it applies your project's conventions.
+- We released a feature in public beta that lets you configure a custom LLM provider. In addition to the default Mendix Platform provider, you can now configure OpenAI-compatible providers or AWS Bedrock on a per-project basis. Mendix still recommends using the Mendix Platform provider for the best experience. For more information, see [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider).
+- Maia is now better at fetching and understanding content from web pages by focusing on the main content.
+- You can now attach Markdown files (*.md*, *.mdx*) to your Maia chat messages. Each file can be up to 50 KB, and you can attach as many as you need. The file contents are sent to Maia as context alongside your prompt.
+- Maia Agent session can be saved by navigating **Help** > **Support Tools** > **Capture Maia Agent Session**, making it easier to share session details when troubleshooting or reporting issues.
+- Data Transformers are now generally available. This allows you to transform complex JSON data, including cases that were never supported before.
+  - You can use a Data Transformer as a preprocessing step before passing the data into an Import Mapping, or use the transformed JSON directly, for example to send data to another system.
+  - Maia support has been added, so Maia can help creating and modifying Data Transformers.
+  - For more information, see [Data Transformer](/refguide/data-transformers/).
 
 ### Improvements