AI Chatbot for Sanity Websites
Your content is structured in Sanity and rendered by the frontend of your choice. Asyntai reads the pages that frontend publishes and answers visitor questions from them, with no schema changes, no GROQ queries and no Studio plugin. Add one snippet to your root layout and redeploy. The assistant in the corner of this page is live, so try it.
See it on your Sanity-powered site
Enter the URL of your deployed frontend and preview answers built from your live content
Structured Content, Conversational Answers
What the assistant adds to a headless site built on Sanity
One Question, the Right Document
Sanity sites often hold hundreds of documents: products, articles, locations, team members. A visitor does not want to browse them all. They ask, for example, which product suits a small office, and the assistant answers from the pages your frontend rendered from those documents.
Learns From the Rendered Site
There is no need to connect the assistant to your dataset. It crawls the public pages your frontend serves, so it sees content exactly as visitors see it. For material outside Sanity, like a pricing PDF or a support handbook, upload the file in the dashboard.
Input for Your Content Model
The conversation log shows which questions visitors ask most. Sometimes the fix is a new article; sometimes it is a missing field in a schema, such as delivery time on a product type. Either way, your editors know what to add in Studio next.
Support That Scales With Your Content
As the number of documents grows, so do visitor questions. The assistant handles the ones your published content already covers, at any hour, and leaves the unusual cases for your team.
Matches Your Design System
Colors, position, avatar, greeting and branding are set in the Asyntai dashboard and update in real time. No component to build, no redeploy for a color change. Test the conversations before your visitors do.
Setup in One Short Video
Follow the steps from account creation to snippet to a live assistant answering questions on a real site.
Put it to the test on this page
Ask the assistant about headless setups, frameworks or pricing and see how it responds
Built Around a Headless Workflow
Studio for editors, your framework for the frontend, Asyntai for visitor questions
No Studio Plugin, No Schema Change
The snippet lives in your frontend layout. Your Sanity project, datasets and schemas stay exactly as they are.
Leads Captured in the Chat
When a visitor asks for a quote, a demo or a sales contact, the assistant requests their email and stores it in your dashboard.
Every Locale You Publish
Whether your frontend serves one language or ten, the assistant answers each visitor in the language of their question.
Guided by Your Instructions
Add rules such as "always link the pricing page" or "offer a demo to companies". The assistant follows them within the limits of your content.
Content That Converts
The work your editors put into structured content pays off twice: once on the page, and again in every answer the assistant gives.
Answers Grounded in Your Pages
The assistant does not invent product details or prices. It answers from your site and documents, and declines unrelated questions.
Add It to Your Frontend Layout
Sanity is headless, so the snippet goes where your pages are rendered. Next.js, Nuxt, SvelteKit, Astro or another framework: the steps are the same.
-
1
Copy your snippet
Create an Asyntai account, enter your website URL and copy the personal snippet from the dashboard.
-
2
Find the root layout
In the frontend project that renders your Sanity content (Next.js, Nuxt, SvelteKit, Astro or similar), open the root layout file, usually
_app.js,layout.tsxorapp.vue. -
3
Add the snippet there
Put the snippet in that root layout so every page loads it, either just before the closing
</body>tag or in the Head component. -
4
Redeploy
Commit, push and redeploy. Once the new build is live, the assistant is available on all pages.
Sign up for free and copy the snippet for your root layout
Why Sanity Teams Pick Asyntai
50 free messages to start, and plans that grow with your traffic
Live Without a Sprint
No integration project, no backend work, no new API route. A developer adds the snippet to the layout in a few minutes, and the rest is configured in the dashboard by whoever owns the content.
Fewer Tickets About Published Facts
If the answer is already in your content, the assistant gives it. Your support team works on the cases that need judgement.
More Sign-Ups From the Same Pages
Visitors with an open question hesitate. Visitors whose question was answered move on to the trial, the demo or the checkout.
Sanity Integration FAQ
Frontends, GROQ, syncing, styling and limits
_app.js, layout.tsx or app.vue in Next.js, Nuxt, SvelteKit or Astro) and paste it before the closing </body> tag or inside the Head component. Redeploy, and it is live. The whole job takes a few minutes.
Headless Content and Visitor Questions: A Guide
What Makes Sanity Different
Sanity is a content platform from a company based in Oslo and San Francisco. Editors work in Sanity Studio, an open source editing app built with React that developers can customize. The content itself is stored as structured JSON in the hosted Content Lake and queried with GROQ, while rich text is kept as Portable Text instead of HTML.
This approach separates content from presentation completely. The same documents can feed a website, an app and a newsletter. For a chat assistant, the presentation layer is what matters: the website your visitors read.
Why the Assistant Reads Pages, Not the Dataset
Raw documents contain drafts, references and fields that only make sense inside your schema. The rendered page is the version you decided to show the public, with the right wording, prices and links.
By crawling that rendered site, Asyntai answers with exactly what visitors are meant to see. You do not have to give it API tokens or worry about unpublished drafts appearing in a conversation.
One Snippet for Any Framework
Teams pair Sanity with Next.js, Nuxt, SvelteKit, Astro, Remix or Gatsby, and some run more than one frontend from the same project. A framework-specific SDK would mean separate work for each one.
The Asyntai snippet is plain JavaScript loaded asynchronously from the root layout. It works the same in every framework, survives framework upgrades and does not add a package to your dependency tree.
Editors Stay in Charge
On a headless site, developers set things up and editors run the content day to day. The assistant follows the same split: the snippet is a one-time developer task, and everything after it belongs to the content team.
Editors upload extra documents, write instructions for tone and topics, and read the conversation history in the Asyntai dashboard, without opening the code repository.
Feeding Questions Back Into Studio
Every conversation is saved and searchable. Patterns appear quickly: a product attribute people always ask about, a policy that is hard to find, a topic with no article at all.
Each pattern is a task for Studio: a new field, a new document, a clearer description. Publish, redeploy, recrawl, and the next visitor who asks gets the improved answer.
Static Builds, Server Rendering and Recrawls
Sanity frontends are deployed in different ways. Some are fully static and rebuilt on every publish, some render on the server, and many use a mix with cached pages that refresh after a while. For the assistant, what counts is the page that is publicly live.
A simple routine works for all of them: when a significant batch of content goes live, start a recrawl in the Asyntai dashboard. The assistant then reads the current version of your pages, including new documents, changed prices and removed products.
Localized Content From One Dataset
Teams that publish in several languages often keep translations in Sanity, either as separate documents or as language fields, and render one route per locale. Visitors arrive on whichever version matches them, but they do not always write in the same language as the page.
The assistant answers in the language of the question, whatever locale the visitor is on. One snippet in the root layout covers every locale, and one Asyntai setup serves all of them.
Instructions as Part of Your Content Strategy
Content teams on Sanity usually think carefully about tone and structure. The same care can go into the assistant's instructions: which pages to recommend, how long answers should be, when to suggest a demo or a contact form. These live in the Asyntai dashboard and can be changed by editors at any time, without a code change or a redeploy.
Let Your Sanity Content Answer Questions
Add the snippet to your layout, redeploy, and use 50 free messages to see what visitors ask.