Embent is an AI agent for your website. It answers visitors only from your own pages — with citations under every answer — captures leads, says "I don't know" instead of inventing, and logs every question it couldn't answer so you know exactly which page to write next. Try it without signing up: paste your URL on embent.com and a preview bot built from your own site is answering in about a minute.
Hi! Congratulations on the launch! Embet looks like an incredibly powerful tool for creating customized AI agents effortlessly.
I have a couple of questions regarding its technical capabilities:
Does it have multi-language support out of the box? If so, which languages are currently supported?
How is the infrastructure handled? Does the agent connect to your own servers via an API, or is there an option for self-hosting/direct API integration?
This seems like a fantastic solution for enhancing website engagement. Wishing you the best of luck today!
Report
21 views
Thank you, Necati, and great questions.
Multi-language: yes, out of the box, in the way that matters most: the agent answers in whatever language the visitor writes in, regardless of the language your site is written in, a Spanish visitor asking about your English docs gets a Spanish answer, still cited to the English page. The widget's own chrome (buttons, placeholders, the lead form) ships in 15 languages today: English, Spanish, Portuguese, French, German, Italian, Dutch, Polish, Turkish, Indonesian, Japanese, Korean, Chinese, Hindi and Vietnamese, auto-detected from the visitor's browser, or pinned per bot. Adding one more is a small data change on our side, so just tell me which one you'd need.
Infrastructure: Embent is fully hosted, nothing to install on your servers. You point it at your public website or docs, our crawler reads the pages, and each bot gets its own isolated index (no shared vector store across customers). Embedding is one script tag. There's no self-hosting option today. The conversation engine is channel-agnostic by design, so a public API and other channels: WhatsApp, Messenger, Telegram, Slack are on the roadmap; if a direct API integration is what you'd use, I'd genuinely like to hear the use case, it helps me sequence it.
Fastest way to see the language behaviour for real: paste your own URL on embent.com (no signup) and ask it something in a language your site isn't written in.
Setup was literally one script tag. It crawls your pages, cites its sources accurately, and captures leads without being pushy. Clean UI, zero bloat, and works exactly as advertised.
Thank you, Necati, and great questions.
Multi-language: yes, out of the box, in the way that matters most: the agent answers in whatever language the visitor writes in, regardless of the language your site is written in, a Spanish visitor asking about your English docs gets a Spanish answer, still cited to the English page. The widget's own chrome (buttons, placeholders, the lead form) ships in 15 languages today: English, Spanish, Portuguese, French, German, Italian, Dutch, Polish, Turkish, Indonesian, Japanese, Korean, Chinese, Hindi and Vietnamese, auto-detected from the visitor's browser, or pinned per bot. Adding one more is a small data change on our side, so just tell me which one you'd need.
Infrastructure: Embent is fully hosted, nothing to install on your servers. You point it at your public website or docs, our crawler reads the pages, and each bot gets its own isolated index (no shared vector store across customers). Embedding is one script tag. There's no self-hosting option today. The conversation engine is channel-agnostic by design, so a public API and other channels: WhatsApp, Messenger, Telegram, Slack are on the roadmap; if a direct API integration is what you'd use, I'd genuinely like to hear the use case, it helps me sequence it.
Fastest way to see the language behaviour for real: paste your own URL on embent.com (no signup) and ask it something in a language your site isn't written in.