Asyntai

Add an image the chatbot may show. The description is what the AI reads to decide when the image answers the question, so describe what it shows and when it helps. Needs the Standard plan or higher, and a website can hold up to 100 images.

Add a titled block of text to one website's knowledge base. The chatbot can use it in answers as soon as this returns. Adds a new entry; it never replaces an existing one.

Fetch one web page and add its text to the knowledge base. Use this for a single page. To take in a whole site, use start_crawl instead.

Add a product the chatbot can show as a card. Needs the Standard plan or higher.

Register a URL to receive events, for example every new message. Returns a signing secret once; store it, because it is never shown again. Needs a paid plan.

Ask one website's chatbot a question and get the answer a real visitor would receive. Use this to test the bot. It spends one message from the account's monthly allowance, and it calls an external model provider.

Add a new website (a new AI agent) to the account and return its embed code. Each plan allows a limited number of websites, and this refuses once that limit is reached. By default it also starts a crawl of the site to build the knowledge base.

Remove one image so the chatbot stops showing it. Needs the Standard plan or higher.

Permanently delete one knowledge base entry and every passage built from it. The chatbot stops using that content immediately. This cannot be undone.

Delete one Proactive Messages rule. The chatbot stops sending that message on the next page a visitor opens. The message log keeps the past entries. To pause a rule instead, use save_proactive_message with enabled false.

Remove one product so the chatbot stops offering it.

Delete one webhook. Events stop reaching that address at once.

Turn a short note (for example: refund approved, 20 EUR, in 5 days) into a full reply to an email conversation, in the customer's language. Nothing is sent: show the draft, then send it with reply_to_email. Spends one AI reply of the plan. Needs Pro or higher.

Turn a short note into a full reply to a ticket's customer, in their language. Nothing is sent: show the draft, then send it with reply_to_ticket. Spends one AI reply of the plan. Needs Pro or higher.

Get the signed-in account's email, plan, and how many chat messages it has used against its monthly allowance.

Get the instructions that shape how one website's chatbot answers: its role, tone and rules.

Summarise one website's chat activity over a period: conversations, messages, leads captured, escalations, and the countries visitors came from.

Read one page of Asyntai's documentation in full, given the url or slug from search_asyntai_docs, for example /documentation/mcp/ or just mcp.

Read the full message history of one conversation, in order, from its session id.

Say whether the daily email summary is on for one website, and when the last one went out.

Show one website's AI email reply settings: on or off, automatic replies or drafts only, the reply delay, the rules, the alert address, the forwarding address and how replies are sent. Needs the Pro plan or higher.

Read one email conversation, oldest first: the customer's emails, the AI's replies and drafts, and the replies the team sent. Needs the Pro plan or higher.

Read the stored text of one knowledge base entry. Works for the content you supplied: text, documents, spreadsheets, single pages and videos. A website crawl is listed but not exported, because the source is your own public site.

Read one order request: the products and quantities, the visitor's name, phone, email, delivery address and note, the internal note and the chat it came from. Needs the Standard plan or higher.

Read one support ticket: its details, the chat that led to it and the emails sent from it, oldest first, and how it can be answered (email needs Pro, chat only for tickets from the website widget). Needs the Standard plan or higher.

Get the full record for one website: its name, domain, platform, widget id and the embed code to paste into the site.

Read the plan-gated features for one website: Real-Time Data Feed and its Max tier, Product Cards, Dynamic Images, User Context, Link Parameters, Chat Retention, Chat Categories, Access Tags, Widget Pinning, Zero Retention, PII Redaction and the Output Classifier. Shows current values, which features the plan allows, and the plan each locked feature needs.

Read all appearance and behaviour settings for one website's chat widget: colours, greeting, position, auto-trigger, data collection, bookings and the rest. Also returns which settings this account's plan cannot change, and the plan each of those needs. The greeting and auto-trigger are one general bubble for every visitor; messages for a click, a page, time on a page or an event are Proactive Messages (list_proactive_messages).

List the visitors currently in a chat: which page they are on, their country, how long they have been there, and whether a human has taken the conversation over. Needs the Standard plan or higher.

Read the record of what changed on this account: who did it, when, and from where. Recorded on the Enterprise plan only.

List the appointment types visitors can book, with length, price and how many spots each has. Bookings needs the Standard plan or higher.

List recent visitor conversations for one website, newest first, with the session id, message count and any email or phone the visitor gave.

List recent crawl jobs for one website with their status, how many pages they took, and why each one stopped.

List the email conversations in one website's Email inbox, newest first: subject, sender, a snippet and whether a person must answer. Needs the Pro plan or higher. Use get_email_thread to read one.

List the third-party tools embedded in the chat, such as a booking calendar or a form. Embeds needs the Standard plan or higher.

List the images the chatbot may show a visitor, with the description that tells it when each one is relevant.

List the sources in one website's knowledge base: uploaded text, documents, added pages and crawls.

List the Knowledge Gaps Asyntai recorded: real visitor questions the chatbot could not answer. Use this to find what to fill in with add_knowledge_text. Needs the Standard plan or higher.

List the email addresses and phone numbers visitors left in chat, newest first, with the page they were on.

List the order requests visitors sent through the order form in the chat: number, status, products, name and phone. An order request is not paid; the team confirms it with the visitor. Needs the Standard plan or higher.

List every Asyntai plan with its price, monthly message allowance and the features it includes, alongside the plan this account is on. Use it to explain which plan includes a feature the account asks about.

The Proactive Messages log: each proactive message a visitor saw, newest first: the rule, when, on which page, in which language, the text, and what the visitor did (opened the chat, closed the bubble, replied). The visitor's name or email is there when the website sends it with User Context. A replied entry has a link to the conversation. Use it to see who saw a message and whether a rule works.

Proactive Messages (the Proactive Messages page in the dashboard, Pro and Enterprise): the chatbot writes FIRST when something happens on the website. Each rule says WHEN (a click on an element, a page address, time on the page, or an event the website's own code sends, such as added_to_cart), WHAT (a fixed text with optional translations, or an instruction the AI writes the message from) and HOW (a bubble above the chat button, or the chat opens). Use this for anything like a triggered message, an automatic message, a message on click, on a page or after some seconds. Returns every rule with its id and its counts for the last 30 days (shown, opened, replied).

List the products the chatbot can show as cards, with price and links. Product Cards needs the Standard plan or higher.

List the people who share this account, what each may reach, and how many seats the plan allows.

List support tickets raised from chat, with status, priority and the visitor's details. Needs the Standard plan or higher.

List what visitors asked the chatbot in a period: the first questions of each conversation, without the chatbot's answers. Use this to find what customers ask about most: group the questions by meaning and give examples. Counts you make by grouping are estimates; say so. When Chat Categories is on, the result also carries exact chat counts per category. To read one conversation in full, use get_conversation.

List the webhooks registered on this account. The signing secret is never returned; it is shown once, when the webhook is created.

List the websites (AI agents) on this Asyntai account, with the id every other tool takes. Start here when the account may have more than one.

List the languages the chat widget has its own wording for, with the greeting and agent name used in each.

Say that the team already answered this email conversation (for example in its own mail program). It leaves the Needs a person list. Nothing is sent. Needs the Pro plan or higher.

Hand a taken-over conversation back to the AI, which answers the visitor again from the next message.

Send an email reply to the customer of one email conversation, in the same email thread and from the website's support address. The customer receives it at once, so show the user the exact wording and get their agreement before calling this. Needs the Pro plan or higher.

Answer a ticket's customer. channel email (Pro or higher) sends an email, and the customer's answer comes back into the ticket. channel chat shows the message in the website chat, only for tickets from the widget. The customer gets it, so get the user's agreement first.

Add a Proactive Messages rule, or change one (pass rule_id from list_proactive_messages; fields you leave out keep their value). The chatbot then writes first, live for every visitor at once, when the trigger happens. For a general greeting bubble shown to everyone, use update_widget_settings instead. Pro and Enterprise only. A fixed text shows at once and costs nothing; an AI rule spends one AI reply each time it shows. On phones the message always shows in a bubble. For trigger_type event, the website must send the event in its code: window.Asyntai = window.Asyntai || {}; (window.Asyntai.events = window.Asyntai.events || []).push({ name: 'added_to_cart', data: { product: 'Running shoes' } });

Search Asyntai's own product documentation and get back the pages that match, with a short excerpt from each. Use this to find out how a feature works before changing anything, rather than guessing. This searches Asyntai's documentation, NOT the customer's own content: for that, use search_knowledge_base. Matching is by keyword, so if the results look wrong, search again using Asyntai's own feature names, for example data feed, widget pinning, access tags, AI instructions.

Search one website's knowledge base and return the passages the chatbot would retrieve for this question, with a relevance score. Use this to check what the chatbot knows about a topic. It does not generate an answer and does not use the message allowance.

Send a message, as a human agent, to a real visitor who is chatting right now. Take the conversation over first. The visitor sees this immediately, so show the user the exact wording and get their agreement before calling this.

Switch Access Tags on or off for one website. Turning it on creates the signing secret your server needs to sign visitor entitlements. Needs the Enterprise plan.

Turn the daily email summary of chats on or off for one website. Needs the Standard plan or higher.

Point the chatbot at a product feed and index it. This fetches the feed, checks it really is a feed, clears whatever was indexed before, and rebuilds the index in the background. Send an empty url to remove the feed. Needs the Standard plan or higher.

Same as set_data_feed, for the Max tier, which indexes a larger catalogue. Fetches, validates, clears the old index and rebuilds it in the background. Needs the Pro plan or higher.

Restrict who can retrieve one knowledge base entry. A visitor must present a matching tag, signed by your own server, before the chatbot will use the entry. Send an empty list to make it public again. Access Tags needs the Enterprise plan.

Freeze the chat widget at its current version, so the site always serves the same copy with an integrity hash. Turning it on builds that snapshot and changes the embed code. Needs the Enterprise plan.

Set the chat widget's greeting, agent name and bubble text for one language. A visitor in that language sees this wording instead of the default.

Crawl a website and add its pages to the knowledge base. Runs in the background; check on it with list_crawls. Each plan caps the pages per crawl, and asking for more than the cap is refused.

Stop the AI answering one conversation so a human can reply instead. The visitor is told a person has joined. Use send_agent_reply afterwards, and release_conversation when done. Needs the Standard plan or higher.

Replace one website's AI instructions with new text. This overwrites the current instructions and changes how the live chatbot answers every visitor. Read them with get_ai_instructions first, and show the user what will change before calling this.

Change one website's AI email reply settings. Pass only the fields to change. Switching replies on needs reply_mode. With auto, the AI emails real customers by itself, so confirm with the user first. Needs the Pro plan or higher.

Set an order request's status (new, confirmed, completed or cancelled) and/or its internal note, which only the team sees. The visitor is not told. Needs the Standard plan or higher.

Set a ticket's status: open, in_progress, resolved or closed. Needs the Standard plan or higher.

Turn website features on or off and set their values, for example the Real-Time Data Feed URL or the PII Redaction rules. Pass an object of field name to value; read them with get_website_features first. A feature the plan does not include is refused with the plan it needs. These change how the live chatbot behaves for every visitor.

Change one or more chat widget settings. Pass an object of setting name to new value; read them with get_widget_settings first. Changes are live for every visitor at once. Settings the plan does not include are refused with the plan they need, and nothing is written unless every value is valid. For a message the chatbot sends by itself on a click, a page, after some seconds or on an event, use save_proactive_message, not the greeting or auto-trigger.