VVitePress × Asyntai50 free messages

AI Chatbot for VitePressDeveloper questions, answered from your docs.

How do I add a custom marker? Does it work with Vue 3? What changed in version 4? Developers ask the same things in issues and chat rooms. The assistant answers from your VitePress pages and links to the right section.

Free plan One head entry Links to your docs
tesseramaps.example/guide/markers
Tessera Maps
Tessera Maps 4.2
MIT licence
TypeScriptVector tilesPlugins
Get started
Tessera MapsOnline
Hi! Need help with Tessera Maps?
Powered by Asyntai
1head entry in your config
Everydocs page
Dayand night replies
50messages on the house
Common asks

Questions your docs get every day

Setup, options, migrations and errors. Asyntai replies with code taken from your guides, plus a link to read on.

How do I install it?How do I add a marker?How do layers work?How do I migrate to v4?Why is my map blank?Does it support touch?
Is there a React wrapper?How fast are vector tiles?Do I need an API key?Can I load GeoJSON?How do I change the style?What is the licence?
Features

Built for VitePress docs

Open-source projects, developer tools and product teams that write their documentation in VitePress.

Knows your docs

Guides, API reference, examples and the changelog, plus extra files you upload.

Getting startedGuide
addMarker()API
Migration v4.pdfLearned

config.mts

The head array in your config.

1entry

Developers worldwide

A developer who writes in Chinese gets the answer in Chinese.

ENZHJADEPTKO

Bug reports collected

Users can leave the steps to reproduce and an email address.

KT
Kenji T.Blank map on Safari
New

Light and dark mode

The chat stays readable when readers switch the VitePress theme.

See where docs fall short

A monthly chart ranks the docs sections behind the most chats.

Migration29%
Layers23%
Styles17%

Honest about versions

It names the version an answer is for.

Does setView() take a zoom option?In version 4, yes: setView(center, { zoom }). In version 3 the zoom was the second argument. The Migration guide shows both.
Example

A developer moves to version 4

A developer upgrades and hits an error. The assistant finds the change in your migration guide.

  • Finds the change

    It answers from your migration guide and API pages.

  • Points to the guide

    A link opens the full migration section.

  • Saves real bugs

    If the docs do not cover it, it collects a report.

Docs colour
Setup

Adding it to a VitePress site

VitePress has a head option in its site config. Entries in it render in the head of every page.

Copy your widget ID

Create a free Asyntai account, enter your docs URL and note the ID in your snippet.

Open your config

Open .vitepress/config.mts (or .js, .ts, .mjs) in your project.

Add a head entry

Put a script item in the head array with the src, the ID and async.

Ship the docs

Run vitepress build and deploy as usual. The chat button now sits on each docs page.

Swap YOUR_ID for your own widget ID. Frontmatter can hold head entries for single pages, but the site config reaches the whole site.

.vitepress config.mts
config.mts
export default { head: [ ['script', { src: 'https://asyntai.com/static/js/chat-widget.js', 'data-asyntai-id': 'YOUR_ID', async: '' }] ] }
Build and deploy
Benefits

Why VitePress projects add it

Begin with 50 free messages. Pick a paid plan as your community grows.

01

A quieter issue tracker

How-to questions get solved on the docs page instead of turning into GitHub issues.

02

A working map sooner

Newcomers reach the right guide quickly and render their first map in minutes.

03

Markdown is the truth

Change a .md file and redeploy. After the next crawl, replies use the new text.

FAQ

VitePress questions

Config, versions, readers and costs.

Where do I add the script in VitePress?

Put a script item in the head array of .vitepress/config. Copy the format from the code box on this page.

Will all docs pages get the chat?

Yes. VitePress renders site config head entries into each page it builds.

Does it work with client-side navigation?

Yes. The script loads once, and the chat button stays on screen as readers move between pages.

Can I add it to one page only?

Yes. VitePress also reads head entries from page frontmatter. Most sites use the site config.

Does it use my Markdown?

Asyntai crawls the built pages that VitePress makes from your Markdown. Crawl again after each major release.

Can it handle several versions?

Yes. Name the current major version in your instructions, and replies mention which version they cover.

Does it work in dark mode?

Yes. The chat window stays readable in the light and dark VitePress themes.

Can developers write in Chinese or Korean?

Yes. Asyntai replies in whichever of 36 languages the developer uses.

Is it free for open-source docs?

The Free plan covers one site with a set of free messages. Paid plans add more messages every month.

Guide

An AI assistant for VitePress docs

Why VitePress projects add an assistant

VitePress makes fast, clean docs from Markdown, with search built in.

Search finds words. Developers often have a goal or an error message, and an assistant can answer that.

Answering setup and usage questions

Install commands, config options and short examples top the list.

Asyntai quotes your guides and links the page, so readers also learn the layout of your docs.

Help during migrations

A major release brings many questions about renamed options and removed features.

The assistant reads your migration guide and gives the new form of the code.

Setup with the head option

VitePress renders entries from the head array in your site config on every page.

One script item, one build and one deploy put the chat on every docs page.

Learning from questions

Your dashboard keeps each conversation, grouped by topic.

Rewrite the guides that readers keep asking about.

Answer every developer on your VitePress docs

One head entry gives every reader a helper. 50 messages cost nothing.

No card required to start.