Skip to main content
Læs siden på dansk An AI bot is a program that works on its own, for example every morning at 7, without a person present. In Studio, the bot gets its own connector of the AI bot type. It connects with the connector’s URL and a key instead of a login.
The bot asks nobody before it writes. The only guard is which tools are in the connector. Give it only the tools it needs.
  • Only administrators can build, change, pause and delete a bot. Only administrators can open the bot’s page.
  • A bot has one own connector, and the connector cannot be shared.
  • The bot belongs to one customer and can only use the customer’s agreements and CVR, like every own connector. See Studio.
  • The bot can only use agreements that are already connected.

​
Platforms

When you build the bot, you choose where it runs. The portal shows the steps for each platform. If you use grok.com with your own account, use an own connector for AI assistants instead. See Own connectors.

​
Build an AI bot

1

Choose AI bot

Open Studio, click Build your own connector, choose AI bot, and click Next.
2

Choose customer, name and platform

Choose the customer, type The bot’s name, for example a name that says what the bot does, and choose the platform under Where does the bot run? The customer cannot be changed afterwards. Click Create it and pick the tools.
3

Choose the tools

The bot starts without tools. Put in the tools it needs. Tools that change data are marked Without human in loop. You can also write Instructions for the bot, so it knows what to do.
4

Go live

Click Go live, and confirm. See the next section.
5

Connect the bot

Copy the URL and the key, and enter them on the platform following the steps in the window. Check The key is used by <bot> only, and click I have saved the key.
A bot costs the same as an own connector. If it is beyond the included ones, the window shows the price before the bot is created. See Price.

​
Go live

The Take <bot> live window shows what the bot is allowed to do.
  • If the connector has tools that change data, they are listed under What <bot> can change without asking. You confirm by typing the bot’s name exactly as it stands. The portal then says The name matches. You can go live.
  • If none of the tools change data, it says, for example, 4 tools in the connector, and none of them change data. There is nothing to confirm.
  • The portal keeps your yes: your name, the time and the tools that change data. It is shown on the bot’s page under Approved risk.
  • Going live costs nothing.
If you later put in a tool that changes data, the bot cannot use it until you have confirmed again. The portal shows A tool that changes data has turned up: confirm again, and the button is called Confirm again. Meanwhile, the other tools work as before.

​
The key

  • The key is shown only once, when it is made. Consile keeps only a fingerprint of it and cannot show it again. If you lose it, you make a new one.
  • The bot sends the key in the header Authorization: Bearer <key>. A key in the URL is refused.
  • The key works only on the bot’s own URL. The address is not a secret. Without the key it cannot be used.
  • The key expires after 180 days. During the last 14 days the portal shows, for example, The key expires in 10 days.
  • Make a new key makes a new key. The old one stops working immediately, and the bot works again once the new one has been entered on the platform.
  • Block the key refuses all calls with the key immediately. The bot and the connector stay, and the bot starts again when you make a new key.
Technical details in English are in Studio connectors and bots.

​
Status and warnings

Each bot has one status in Studio, on the bot’s page and on Team. Three warnings are shown only to administrators:
  • Used from 2 places: The key has been used from two different addresses within 10 minutes. If you do not know both places, pause the bot, and make a new key.
  • The key expires in … days: Make a new key, and enter it on the platform.
  • Confirm again: A tool that changes data has been added. The bot cannot use it until you have confirmed.
If one of the customer’s agreements is no longer connected, the bot’s page shows, for example, Shopify is not connected. The bot gets an error on every call until the agreement is connected again.

​
Pause and resume

Click Pause on the bot’s page. Calls with the key are refused immediately. The key is kept, so the bot works again when you click Resume.

​
Call limits

The Use and limits card shows how many calls the bot has made today, and the highest number in one minute. The Calls per day chart shows the last 14 days.
  • From the start, the bot may make at most 30 calls per minute and 1,000 calls per day.
  • With Change limits you can lower the limits. They can never go above 30 calls per minute and 1,000 calls per day.
  • Above the per-minute limit, calls are refused for the rest of the minute. The number of calls today resets at midnight UTC, which is 1 am in winter and 2 am in summer Danish time.

​
Bot activity

The Activity card on the bot’s page shows every call the bot has made, newest first, with the time, tool, result and the address the call came from.
  • The result is OK, Error or Refused. For a refusal, the reason is shown, for example Over the limit for calls, The bot is paused, Not in the connector or The portal is not connected. Portal is Studio’s word for an agreement.
  • Over the account’s monthly calls means that the organization has used the calls its plan gives. See The free edition.
  • Waiting for approval means that the tool requires approval. See Approvals.
  • The log keeps calls for 30 days. It never shows data from the customer’s system.

​
Price

A bot is priced as an own connector, never as a user.
  • The bot counts against the included own connectors of the administrator who built it, together with own connectors for AI assistants. See How many own connectors can you have?
  • Beyond the included ones, it costs the same as an extra own connector under the Consile Studio membership, 49 DKK/month excl. VAT (€6.50). The price is shown when the bot is created.
  • The bot takes no place as a user, and going live costs nothing.

​
Deactivate or delete the bot

At the bottom of the bot’s page, under Deactivate, block or delete:
  • Deactivate the bot: The bot does not count against the included ones and is paused. Its name, tools and key are kept. If you activate it again, it stays paused until you click Resume.
  • Block the key: All calls with the key are refused until you make a new key.
  • Delete the bot: The bot, its connector and the key are deleted, and calls are refused immediately. You confirm by typing the bot’s name. It cannot be undone.
If an administrator removes the person who built the bot from the team, the bot is deactivated and paused. Another administrator can activate it again and then becomes responsible for it.

​
AI bots under Team

If the organization has at least one bot, Team shows the AI bots card below the people, and the tab is called People and bots. Everyone in the organization can see which bots exist, which customer they belong to, how many tools they have, and who is responsible.
Bots take no seat and do not log in. Each bot has its own connector in Studio and can do only what is in it.
Administrators have the Go to the bot button and see the three warnings.