Xedant Agent can be connected to Chatbot Agent — an AI agent that knows how to work with your project’s files. Bots are exactly those project files, so the agent can edit them itself, on your verbal request. The pairing is optional: without it, everything else works as usual.
How to connect
Set the address and key of your Xedant Agent when the application starts — with the AGENT_API_URL and AGENT_API_KEY variables. Without them all agent chat surfaces are simply hidden, and the other capabilities work as before. If you install Chatbot Agent through Xedant MultiAgent, MultiAgent sets up the pairing itself.
What it can do
You can say in words: “add product return handling”, “make the greeting friendlier”, “count how many people asked about delivery” — and the agent will fix the scenario, scripts and bot settings itself. It makes all edits in the same files you see, so nothing is hidden: the result can be checked in the studio and in the version history.
How to call it
There are three entrances. The Call Agent button on the bot’s page — its prompt already carries that bot’s context. The separate “Chats” section with the list of conversations, token and cost counters. And the chat panel at the bottom of the screen, always at hand.
What the panel shows
The panel shows messages, tool calls with file changes, the task list and the message queue. Everything streams live as the work happens, so it is clear what the agent is doing right now and what it has already changed. If you want to adjust the task on the fly or ask a clarifying question — that happens here too.
Skills and environments
The agent has its own skills — ready-made abilities for typical tasks — and its own model choice. A new chat opens with the chatbot skill already selected, so there is no need to pick it by hand: you can still take another skill or turn the choice off. Background chat sounds are configured separately, so they do not distract while the agent works on its own.
License
Sending messages to the agent and answering its questions requires a license — that is the only thing it restricts. Everything else — bots, the studio, the emulator, the knowledge base, operators, broadcasts, analytics — works without a license. The license comes with the Agent Factory subscription.
Managing bots over the API
Bots can be managed not only with the mouse but also with commands over the network — the agent and your own integrations use the same surface. Access opens with the management key CHATBOT_APP_HASH — the variable stores not the key itself but its fingerprint (the SHA-256 hash in hexadecimal form). Requests carry the key in the X-API-Key header. Secrets are never returned in responses: tokens and passwords arrive masked. If the management key is not set, this path is disabled and only ordinary sign-in works.
The API exposes everything needed to work without the interface: bots and their scenarios, the media library (upload, download and delete the pictures and files a scenario references), the service settings — record retention periods, the broadcast recipient limit and the application address — as well as the list of libraries for scripts and marking conversations as read in the Inbox. This way a bot can be assembled, checked and published with commands alone, without opening a browser.
Next: a general introduction — in the Getting Started section, the anatomy of a bot — in Bots, and configuring the models the agent uses — in Models & Prompts.