Add a team of AI agents to your Gatsby site — a support agent grounded in your content that answers with cited sources and can reach your tools via MCP, asking before it changes anything. Gatsby's SSR API makes embedding a one-file change.
What your visitors get
A visitor with a question gets an instant, cited answer pulled from your own pages rather than a generic guess. Behind the widget, AIML.chat runs a Support agent grounded in your content and tool-calling agents that act through the Model Context Protocol (MCP), with human write-confirm on anything that changes data. Every answer links to the exact source page, so trust stays high. It also captures a lead when it can't fully answer, so you never lose a visitor, and the analytics surface the questions your content doesn't yet cover.
Add it in three steps
- 1Create a website in AIML.chat and point the crawler at your site's URL (or connect its GitHub repo). It indexes and embeds your pages automatically.
- 2Add the widget embed snippet via
gatsby-ssr.jsusing thesetPostBodyComponentsAPI (oronRenderBody), so it ships on every statically rendered page. - 3Build and deploy. The widget appears site-wide, themed to match, and stays current as you re-crawl.
Because Gatsby pre-renders to static HTML and the widget is vanilla JS under 30KB gzipped, your site stays fast. As your content changes, a re-crawl — manual, scheduled, or via the GitHub Action on every push — keeps answers accurate. For other React stacks, see the Next.js and Astro guides.
How do I embed it in Gatsby?+
Use gatsby-ssr.js with setPostBodyComponents (or onRenderBody) to inject the widget embed snippet on every page.
Will it slow my Gatsby site?+
No. Gatsby pre-renders static HTML and the widget is under 30KB gzipped, so performance stays strong.
Is there a free plan?+
Yes — 100 messages a month and one website on the free tier. See pricing for higher limits.