Navigate through the Mendix Cloud GenAI Portal
Introduction
The Mendix Cloud GenAI portal is an online platform that provides access to Mendix Cloud GenAI resource packs. These resource packs on Mendix Cloud enable seamless integration with Generative AI technology, provisioned and hosted by Mendix:
- GenAI Model Resource Packs provide access to model resources: Anthropic’s Claude and Cohere’s Embed.
- GenAI Knowledge Base Resource Packs provide the infrastructure to deliver retrieval-augmented generation (RAG) architecture and other GenAI use cases requiring a vector database.
GenAI resource packs accelerate the delivery of complete generative AI solutions within Mendix apps that seamlessly integrate with GenAI technology. Learn more by following these links to Mendix Cloud GenAI Resource Packs and the Mendix Cloud GenAI Connector. To start with a GenAI-infused Mendix application, see creating a chatbot using the AI Bot Starter App or building a GenAI app from scratch with the Blank GenAI App.
Resource Details
Settings
The Settings tab contains the details of a GenAI resource. It shows the following:
- Display Name: indicates the name of the resource.
- ID: indicates the resource ID.
- Region: the region where the resource is hosted.
- Cloud Provider: indicates the cloud provider, for example, AWS.
- Type: this is the type of resource, for example, Text Generation, Embedding, Knowledge Base, etc.
- Model: indicates which model is used, for example, Anthropic Claude Sonnet 3.5.
- Plan: indicates the subscription plan used for compute resources (for example, embedding or text generation resources).
- Environment: shows which environment is used, for example, test, acceptance, or production.
When you are looking at the knowledge base resource settings, you will also see details of the associated embeddings resource and vice versa. To learn more about embeddings, see the Embedding vector section of RAG in a Mendix App.
Team
The Team page allows you to manage access to the Mendix Cloud GenAI resource. All users listed in this overview have access to the resource in the GenAI resource portal and can create new keys or invite new users. You can add new users via the Add Member button and remove them using the Remove Member button next to their name in the overview.
Keys
The Keys tab allows you to manage configuration keys for the resources. These keys provide programmatic access to the GenAI resources. From the Keys tab, you can create new keys and revoke existing ones.
To create a new key, click Create Key, add a description, and save the changes. A pop-up message will display the key.
Once created, the key can be used in the Mendix application via the Mendix Cloud GenAI Connector. When you create a key for a knowledge base, an embedding key is automatically generated and marked accordingly in the keys overview.
Content (Only for Knowledge Bases)
On the Content page, you can find information on adding knowledge to your Knowledge Base resource and managing its content.
Currently, you have the following options for adding data to a Knowledge Base:
- Add files (for example, TXT or PDF)
- Add data from a Mendix application
Add Files
When you select the Add Files Like .TXT or .PDF option, you can upload documents directly to the GenAI portal. Before uploading, you also have the option to add metadata. For more information, see the metadata section below.
Metadata
Metadata is additional information that can be attached to data in a GenAI knowledge base. Unlike the actual content, metadata provides structured details that help in organizing, searching, and filtering information more efficiently. It helps manage large datasets by allowing to retrieve of relevant data based on specific attributes rather than relying solely on similarity-based searches.
Metadata consists of key-value pairs and serves as additional information connected to the data, though it is not part of the vectorization itself.
For example, a GenAI Knowledge Base could be used to store customer support tickets. Each ticket may have associated metadata such as Ticket Type, Status, and Priority. Instead of relying solely on similarity-based searches of ticket descriptions, users can filter for specific tickets, such as ‘bug’ tickets with the status set to ‘solved’.
Add Data from a Mendix Application
You can upload data directly from Mendix to the Knowledge Base. To do so, several operations of the Mendix Cloud GenAI Connector are required. For a detailed guide on this process, see the Add Data Chunks to Your Knowledge Base section of Mendix Cloud GenAI Connector.
Token Consumption Monitor
The Token Consumption Monitor shows detailed graphs of the token consumption used by the GenAI resource. Use this overview to see the current usage, insights on the usage per day, and to compare the current month with previous months.
What Are Tokens?
Tokens are what you pay for when consuming large language model services.
In order for a large language model to understand text input, the text is first ‘tokenized’: broken down into smaller pieces where each piece represents a token with its unique ID. A good rule of thumb is that 100 tokens are around 75 English words, however there are always differences depending on the model or the language used. After tokenization, each token will be assigned an embeddings vector. The tokens required to feed the input prompt to the model are called ‘input tokens’. The tokens required to transform the model output vectors into, for example, text or images are called ‘output tokens’.
When Are Tokens Consumed?
Text generation resources consume both input and output tokens (text sent to the model and generated by the model).
Embeddings resources only consume input tokens. This is because only the generated embedding vectors are returned and the generated output is not tokenized.
Knowledge base resources do not consume tokens as they only store embedding vectors. Uploading a document to a knowledge base connected to an Embeddings resource will consume tokens in the embeddings resource.
Exporting Token Consumption Data
Click Export to export consumption data in CSV format. The export contains basic information about input tokens, output tokens, and dates. Days with no consumption are not exported.