One API for leading AI models

MaaSLink is a model-service platform for enterprises, development teams, and channel partners. It brings text, image, audio, video, and vector models into one service, so teams can create API keys, make calls, and review usage and quotas without learning a separate workflow for every provider.

Before choosing a model, open the model catalog to see what is currently available, which inputs and outputs it supports, and the price shown for the current site. Then follow the online documentation to complete a test integration before moving the workload into production. This keeps your test configuration aligned with the model you plan to use.

Model availability, features, and prices can change as the catalog is updated, so use the information shown on the site when you make a decision. To learn more about the platform's background and service focus, visit About us.

To make a first MaaSLink model call, create an account and an API key, confirm the Base URL for the current site, and copy a model ID from the model catalog. Keep the API key in a server-side secret manager; do not place it in browser code, a public repository, or application logs.

Next, follow the online documentation to configure a compatible client or send the API request directly. Check that the response matches the input and output requirements of the model you selected, and run the whole process in a test environment before using it in production.

If a call fails, check the Base URL, model ID, account balance or quota, authentication header, and request format in that order. Model prices, rate limits, and supported features can change, so confirm the current catalog entry before launch. The complete setup steps and common troubleshooting guidance are available in the Documentation section.

A channel partner can use MaaSLink to link approved customer accounts, set balances or limits within its authorized scope, and review usage by customer, model, or API key. This keeps customer operations, credentials, and metering in one workflow instead of requiring every team to build its own management system.

Before delivering a service, confirm the customer relationship and the permissions available to the account. Quotas, settlement, and service scope should follow the agreement with the customer, while the models and features that can be used depend on the current account and catalog.

Review each customer link and quota change in the console before it takes effect. The channel workflow and step-by-step instructions are available in Documentation, and current model details and prices are listed in the model catalog. Check both before confirming a customer deployment.