Asyntai
Run your website's AI support agent: knowledge, conversations, leads and live replies.
| Endpoint | https://asyntai.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 59 tools · grade D (57) · pin ts_a045b537fe5a0de004c0e65ac09b8547 · protocol 2025-06-18 |
| First / last listed | 2026-10-28 00:39 UTC / 2026-10-28 00:39 UTC |
| Grade over time | 2026-10-28: D (57), 59 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: list_websites get_account list_plans search_asyntai_docs get_asyntai_doc get_website create_website get_widget_settings update_widget_settings set_data_feed set_data_feed_max set_access_tags set_widget_pinning get_website_features update_website_features search_knowledge_base list_knowledge add_knowledge_text delete_knowledge_entry get_ai_instructions update_ai_instructions get_knowledge_entry add_knowledge_url set_knowledge_tags start_crawl list_crawls list_conversations get_conversation list_leads get_analytics list_visitor_questions list_knowledge_gaps list_images add_image delete_image list_products add_product delete_product list_booking_types list_embeds list_tickets list_webhooks add_webhook delete_webhook list_active_sessions take_over_conversation release_conversation send_agent_reply get_daily_report set_daily_report list_audit_log list_team_members list_widget_translations set_widget_translation list_proactive_messages save_proactive_message delete_proactive_message list_proactive_message_log ask_ai
list_websites | 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. params: none |
get_account | Get the signed-in account's email, plan, and how many chat messages it has used against its monthly allowance. params: none |
list_plans | 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. params: none |
search_asyntai_docs | 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 featur params: query*, limit |
get_asyntai_doc | 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. params: page* |
get_website | Get the full record for one website: its name, domain, platform, widget id and the embed code to paste into the site. params: website_id |
create_website | 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. params: domain*, name, crawl |
get_widget_settings | 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 Mes params: website_id |
update_widget_settings | 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 sav params: settings*, website_id |
set_data_feed | 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. params: url*, enabled, website_id |
set_data_feed_max | 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. params: url*, enabled, website_id |
set_access_tags | 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. params: enabled*, website_id |
set_widget_pinning | 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. params: enabled*, website_id |
get_website_features | 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. params: website_id |
update_website_features | 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. params: fields*, website_id |
search_knowledge_base | 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. params: query*, website_id, limit |
list_knowledge | List the sources in one website's knowledge base: uploaded text, documents, added pages and crawls. params: website_id, limit |
add_knowledge_text | 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. params: title*, content*, website_id |
delete_knowledge_entry | Permanently delete one knowledge base entry and every passage built from it. The chatbot stops using that content immediately. This cannot be undone. params: entry_id* |
get_ai_instructions | Get the instructions that shape how one website's chatbot answers: its role, tone and rules. params: website_id |
update_ai_instructions | 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. params: instructions*, website_id |
get_knowledge_entry | 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. params: entry_id* |
add_knowledge_url | 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. params: url*, website_id |
set_knowledge_tags | 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. params: entry_id*, access_tags* |
start_crawl | 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. params: website_id, start_url, max_pages |
list_crawls | List recent crawl jobs for one website with their status, how many pages they took, and why each one stopped. params: website_id, limit |
list_conversations | List recent visitor conversations for one website, newest first, with the session id, message count and any email or phone the visitor gave. params: website_id, days, limit, with_leads_only |
get_conversation | Read the full message history of one conversation, in order, from its session id. params: session_id*, limit |
list_leads | List the email addresses and phone numbers visitors left in chat, newest first, with the page they were on. params: website_id, limit |
get_analytics | Summarise one website's chat activity over a period: conversations, messages, leads captured, escalations, and the countries visitors came from. params: website_id, days |
list_visitor_questions | 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_co params: website_id, days, per_chat, limit |
list_knowledge_gaps | 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. params: website_id, days, limit, include_resolved |
list_images | List the images the chatbot may show a visitor, with the description that tells it when each one is relevant. params: website_id |
add_image | 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. params: image_url*, description*, website_id |
delete_image | Remove one image so the chatbot stops showing it. params: image_id* |
list_products | List the products the chatbot can show as cards, with price and links. Product Cards needs the Standard plan or higher. params: website_id |
add_product | Add a product the chatbot can show as a card. Needs the Standard plan or higher. params: name*, description, price, product_link, image_url, website_id |
delete_product | Remove one product so the chatbot stops offering it. params: product_id* |
list_booking_types | List the appointment types visitors can book, with length, price and how many spots each has. Bookings needs the Standard plan or higher. params: website_id |
list_embeds | List the third-party tools embedded in the chat, such as a booking calendar or a form. Embeds needs the Standard plan or higher. params: website_id |
list_tickets | List support tickets raised from chat, with status, priority and the visitor's details. Needs the Standard plan or higher. params: website_id, status, limit |
list_webhooks | List the webhooks registered on this account. The signing secret is never returned; it is shown once, when the webhook is created. params: none |
add_webhook | 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. params: url*, events*, website_id |
delete_webhook | Delete one webhook. Events stop reaching that address at once. params: webhook_id* |
list_active_sessions | 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. params: website_id, limit |
take_over_conversation | 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. params: session_id* |
release_conversation | Hand a taken-over conversation back to the AI, which answers the visitor again from the next message. params: session_id* |
send_agent_reply | 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. params: session_id*, message*, agent_name |
get_daily_report | Say whether the daily email summary is on for one website, and when the last one went out. params: website_id |
set_daily_report | Turn the daily email summary of chats on or off for one website. Needs the Standard plan or higher. params: enabled*, website_id |
list_audit_log | Read the record of what changed on this account: who did it, when, and from where. Recorded on the Enterprise plan only. params: days, limit, category |
list_team_members | List the people who share this account, what each may reach, and how many seats the plan allows. params: none |
list_widget_translations | List the languages the chat widget has its own wording for, with the greeting and agent name used in each. params: website_id |
set_widget_translation | 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. params: language_code*, ai_support_name, initial_message, notification_bubble_text, website_id |
list_proactive_messages | 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 params: website_id |
save_proactive_message | 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 r params: rule_id, name, enabled, trigger_type, trigger_value, message_mode, message_text, translations, display, frequency, website_id |
delete_proactive_message | 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. params: rule_id*, website_id |
list_proactive_message_log | 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. params: rule_id, limit, before_id, website_id |
ask_ai | 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. params: message*, website_id, session_id |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.