Alaio Vibecode: Build an App for Bitrix24 with an AI Agent
- When to Use Alaio Vibecode
- How the Alaio Vibecode API Differs from the Bitrix24 REST API
- How Much Alaio Vibecode Costs
- FAQ
- Can I build an app for Bitrix24 with Codex, Claude Code, Cursor, or another AI tool?
- Do I need to know Bitrix24 REST API methods in advance?
- Can I create a server manually?
- Where does the app code run?
- Can I use external libraries?
- What limits does the Vibecode API have?
- Can I use Alaio Vibecode without Bitrix24?
- How do I debug an app if the agent got something wrong?
- What restrictions do Black Hole servers have?
- How do I update an app?
- Can several employees work on the same app?
- Why can't I create a key or an app?
- What's Next
Alaio Vibecode is a platform for building Bitrix24 apps with AI agents. You can build an app in four steps, without knowing any programming language:
-
Get a Vibecode key.
-
Give the key to an AI agent.
-
Describe the task in plain language, the way you would explain it to a colleague.
-
Get a ready-made app for Bitrix24.
The platform works with AI agents that can read documentation, write code, and run commands in a project: Codex, Claude Code, Cursor, and others.
The AI agent reads the Vibecode documentation, retrieves the available platform capabilities, and writes the app code. If the app needs a backend, event handlers, or background logic, the agent can create a Black Hole server and deploy the app with no manual hosting setup.
-
Vibecode Quick Start — technical documentation
-
Alaio Vibecode: Getting Started — user documentation
When to Use Alaio Vibecode
Vibecode fits scenarios where you need to build an app for Bitrix24 and hand part of the technical work to an AI agent: finding API methods, setting up authorization, writing the code, and preparing the launch.
The platform fits tasks where you need to:
-
build an app for working with CRM, tasks, chats, files, or the calendar,
-
prepare an internal dashboard based on Bitrix24 data,
-
create a chatbot for employees or clients,
-
automate a repetitive process through an app,
-
launch a server-side app without setting up a server yourself,
-
validate an app idea before full-scale development.
The agent does not need to look for REST API method documentation. It retrieves the documentation, the available objects, and the platform rules from Vibecode, and then picks a suitable way to solve the user's task.
How the Alaio Vibecode API Differs from the Bitrix24 REST API
The Bitrix24 REST API is the main API for working with Bitrix24. The Vibecode API is a separate API for building apps with AI agents. Some Vibecode API methods call the Bitrix24 REST API, but they simplify and optimize the calls.
-
They convert data to the required format. For example, they transform field names and filters before calling the REST API.
-
They retrieve more data in a single request. Where the REST API returns data in batches of 50 items, the Vibecode API can split the request into batches itself and assemble a result of up to 5,000 items.
-
They run bulk requests and retry calls on temporary errors.
Vibecode also has its own methods that the Bitrix24 REST API does not provide, for example, for creating Black Hole servers and connecting AI models.
How Much Alaio Vibecode Costs
Working with Vibecode requires a paid Bitrix24 plan and a Bitrix24 Vibe+ subscription. Any Vibe+ plan comes with extended AI capabilities, a catalog of 700+ apps, and full access to building apps, bots, and AI tools.
Resource-intensive scenarios are billed separately, pay-as-you-go, in the platform's internal currency — Vibe credits, marked as Ꝟ. These are Black Hole servers, metered AI models, AI search, and AI agents. One Vibe credit equals one dollar.
Server cost depends on its capacity and actual running time. AI search cost depends on the search mode and the selected provider.
The welcome bonus is 10 Vibe credits. It is credited automatically to new companies that have not purchased paid Bitrix24 licenses before, and it is valid for up to 12 months or until it is used up.
Spending can be capped. An administrator sets a monthly budget for the entire Bitrix24 and for an individual employee. When the budget is exhausted, calls that spend credits respond with a 402 status error — work under the subscription continues.
FAQ
Can I build an app for Bitrix24 with Codex, Claude Code, Cursor, or another AI tool?
Yes. Create a Vibecode key, give the AI agent the link https://vibecode.bitrix24.com/v1/me, and describe the app. In your request, you can explicitly state that Vibecode and the Vibecode documentation must be used. The agent must be able to read documentation, write code, and run commands in the project. If the AI tool supports MCP, it can also use the Vibecode MCP integrations. For a step-by-step scenario, see How to Build Your First App.
Do I need to know Bitrix24 REST API methods in advance?
No. The AI agent retrieves the Vibecode documentation and the platform API methods for the task. That said, the developer must review the resulting code, the access permissions, and the way the app works.
Can I create a server manually?
Yes. You can create a server in the Vibecode interface, in the Black Hole section. Alternatively, ask the AI agent to create the server and deploy following the Vibecode instructions.
Where does the app code run?
A static HTML/JS app can be hosted without a backend. If the app needs a backend, a database, event handlers, or background jobs, it can run on a Black Hole server. For details, see Where the App Runs.
Can I use external libraries?
Yes. For static HTML/JS apps, use libraries that can be shipped with the app or connected through a public link. For server-side apps, the restrictions depend on the Black Hole server.
What limits does the Vibecode API have?
By default, a key is limited to 300 requests per minute. Individual methods have lower limits: AI search POST /v1/search is limited to 60 requests per minute. The AI router has its own limits: 600 requests per minute per key and 1,500 requests per minute per user. If an app exceeds a limit, Vibecode returns a 429 status error: the response contains the limit and the time after which the request can be repeated. In that case, the app must wait and retry later.
The effective limit value comes in the X-RateLimit-Limit header — it may be lower than the numbers above.
Can I use Alaio Vibecode without Bitrix24?
Alaio Vibecode is designed for building Bitrix24 apps. Access to Bitrix24 is required to get a key, work with account data, install apps, and run bots. Some Vibecode tools, such as AI models or AI search, can be connected to the app code on their own, but the platform's main scenario is tied to Bitrix24.
How do I debug an app if the agent got something wrong?
Tell the agent what is not working: the error text and the action that failed. Based on this information, the agent can correct the request parameters, pick a different method, add error handling, or report which permissions the key is missing. For what the agent does automatically on errors, see What the AI Agent Does Automatically.
What restrictions do Black Hole servers have?
Server parameters depend on the selected plan: CPU, RAM, disk, region, and cost are shown when you select a server. By default, the limit is up to 5 servers per user and up to 100 servers per API key. An administrator sets custom values in the Vibecode configurations — the number of keys and bots per user is limited there as well. If a limit is exceeded or server creation is disabled by the configurations, Vibecode returns an error. For more about servers, see Black Hole Servers.
How do I update an app?
Describe the changes to the AI agent. The agent can modify the code, verify the scenario, and deploy again through Vibecode. After the update, check the permissions, the data, the API errors, and the app's main scenario. Vibecode retains a source code version on every deployment, so you can roll back to a previous version if something goes wrong — for details, see App Version History.
Can several employees work on the same app?
Yes. The server owner assembles a development team and assigns roles to its members: everyone works with their own key, and there is no need to share someone else's key. An app can also be handed over to another employee in full — together with the keys, the server, and the sources. For details, see Collaborating on an App.
Why can't I create a key or an app?
Creating keys, apps, servers, bots, and agents is restricted by the Vibecode configurations, while issuing a webhook and installing an app is restricted by the Bitrix24 security configurations. The error code shows which setting is blocking you. If you are not an administrator, submit an access request from the Vibecode dashboard. For details, see Permissions for Creating Keys and Apps.
What's Next
Vibecode connects the user's task, the AI agent, and the Bitrix24 documentation in a single development scenario. To build an app, get a key, give the agent the link https://vibecode.bitrix24.com/v1/me, describe the task, and check the result in your Bitrix24.
Other articles in this section:
-
How to Build Your First App — development steps, key types, key security, prompts, and result verification
-
Vibecode Tools — Black Hole servers, bots, AI models, AI search, storage, and other tools
-
Collaborating on an App — the server development team, member roles, and handing an app over to another owner