AI Chatbot for VuePress Documentation

Documentation search matches words; readers arrive with symptoms. One head entry in your VuePress config adds an assistant that answers from the same pages, in whatever language the reader used.

Get Started Free See Pricing

Try it on your own docs for free

Enter your docs URL and see how an AI assistant would answer readers

See It In Action

For project documentation and technical handbooks built with VuePress

AI answering documentation questions by symptom

Answers Symptoms, Not Keywords

A reader with an error searches the error text; your docs describe the concept. Search returns nothing useful and they conclude the documentation is incomplete when the answer was two pages away.

Adding the Asyntai script to a VuePress config

One Head Entry in Your Config

VuePress config has a head array for exactly this. Add the script there and it applies across every page of the site, in every locale you build.

AI answering multilingual documentation questions

Covers Every Locale You Publish

Multilingual docs usually have one well-maintained language and several that lag. The assistant answers in 36 languages from whatever pages exist.

Reviewing questions to find documentation gaps

Shows Which Pages Are Missing

Every unanswered question is a documentation gap with evidence attached. That is a far better backlog than guessing what readers need.

AI added without a VuePress plugin

No Plugin, No Theme Fork

Nothing is installed and no theme is forked, so upgrading VuePress or switching theme does not involve it.

Have any questions? Try our AI chatbot right now

Ask it anything - it is live on this page

Built for VuePress Merchants

A head entry in config.js. Nothing forked, nothing installed.

Symptom-First Answers

Readers describe what happened; the assistant finds the relevant page.

Config Entry Only

No plugin, no theme fork, nothing to migrate at upgrade time.

Every Locale Covered

36 languages from one entry, whatever your i18n setup.

Gap Detection

Unanswered questions become a documented backlog.

Lighter Than Your Logo

The whole assistant weighs less than a hero image and arrives after the page is drawn.

No Invented API

It answers from your pages rather than guessing at behaviour.

Simple VuePress Integration

One head entry covers the docs site, across every locale.

  1. 1

    Open an account and take the tag

    Register, hand over the docs URL so the crawler can walk your handbook, and lift the tag from the dashboard.

  2. 2

    Open your VuePress config

    Add the script to the head array so it is emitted on every page.

  3. 3

    Ship it with the next build

    The tag lands in the generated output. No plugin lifecycle, no theme override.

  4. 4

    Tune it away from the repo

    Voice, house rules, extra reference files and styling all live in the dashboard, not in version control.

Get Your JavaScript Snippet

Sign up free and get your personalised snippet instantly - paste it once and the widget is live

Why Documentation Teams Choose Asyntai

Start free with 100 messages, upgrade as docs traffic grows

Fewer Support Issues

Questions answered in the docs stop arriving as issues and tickets.

A Real Documentation Backlog

Reader questions show exactly which pages to write next.

Non-Native Readers Served

Answers in the reader’s language reduce the penalty of docs written only in English.

Ready to add an AI assistant to your docs?

Start free with 100 messages. No credit card required.

Create Free Account

Frequently Asked Questions

What documentation teams ask first

How do I add it?
Add the script to the head array in your VuePress config. It is then emitted on every page of every locale.
Is there a plugin?
Not needed. A head entry avoids both plugin compatibility and forking the default theme.
Does it work with multiple locales?
Yes. One entry covers all of them, and the assistant answers in the reader’s language regardless of which locale they are reading.
Where does its knowledge come from?
Your built documentation pages, crawled on demand, plus uploads for anything not published.
Can it answer API questions accurately?
It answers what your docs state and says when something is undocumented rather than inferring behaviour, which is the only safe default for API references.
Any cost to page speed?
Nothing you could measure. It is a small file requested once the page has already painted.
Can I scope it to one version of the docs?
Yes. Add it to the config for that version only if you build versioned docs separately.
What if we exhaust the monthly allowance?
Replies stop until the counter rolls over, unless you raise the ceiling first. The free tier carries a hundred conversations, Starter twenty-five hundred.
We publish handbooks for three teams. Workable?
Each site is isolated — its own crawled corpus, its own instructions, its own transcripts. One on Free, two on Starter, three on Standard, twenty on Pro.

What an AI Assistant Adds to Technical Documentation

Search Rewards People Who Already Know

Documentation search is a keyword match, and readers who need help most are precisely those who do not know the right keywords. They search the error, the symptom, or their own paraphrase, and get nothing.

Answering conversationally closes that gap without rewriting anything. The docs were adequate; the entry point was not.

Unanswered Questions Are Free Research

Documentation teams argue about priorities based on intuition and analytics that only show what was read. Neither shows what readers wanted and failed to find.

Logged questions do exactly that, with volume attached. It is the cheapest documentation research available and it accumulates automatically.

Docs Questions Become Engineering Interruptions

When documentation cannot answer a question, the reader asks a human: an issue, a support ticket, a message to a maintainer. Each one interrupts someone expensive.

Deflecting the documented layer protects that attention. Maintainers keep the questions that genuinely need their knowledge.

English-Only Docs Have a Hidden Cost

Most technical documentation is written in English and read by people for whom it is a second language. That gap slows adoption in ways nobody measures.

Answering in the reader’s own language removes part of that friction immediately, without translating a single page.

Config Entries Survive Upgrades

Plugins and forked themes are the two things that make documentation site upgrades painful. Both accumulate quietly and both eventually block a version bump.

A head entry avoids both. Upgrading VuePress or changing theme leaves the assistant working, and removing it is deleting one line of config.

Ready to Let Your Docs Answer Readers?

Start free with 100 messages and add one entry to your config.

Start Free - No Credit Card Required