These docs describe the current Dante AI platform. On the earlier platform? Your API reference is at api-v2.dante-ai.com/docs (sign-in needed), and your key goes in the x-api-key header.
Embedding your agent
One line of code, paste it onto your website, your agent appears. No deploy step on your end, no build pipeline, no CDN config.
Open your agent's Publish page, then go to the Install tab โ
Two ways to embed
- Floating AI agent. A circular launcher button appears in the bottom right corner of every page. Visitors click to open. This is what most customers use.
- Script embed. Drops the chat into your page as a full-page panel or any size you want. It's a small snippet (a div plus our embed.js), not a raw iframe tag, and embed.js mounts the panel itself, which is what keeps your domain lock working. Use this for a dedicated /contact page, a help centre, or any standalone chat layout.
Step by step
- Open your agent's Publish page and switch to the Install tab.
- Pick the embed type, Floating or Script.
- Add your website's hostname to Allowed domains (e.g.
example.com) so nobody else can run your snippet on their site. - Click Copy embed code.
- Paste the snippet into your website's HTML, right before the closing
</body>tag.
Where to paste it
The Go live page and the Ready to go live window in Backstage show the same builder guide. Search for your site builder, pick it, and you get three exact steps for it. Where a builder or a plan cannot add a script to every page, the guide says so. Here is that guidance for each one.
- Any HTML site: Open the HTML for your page, or your site-wide template or footer. Paste the code, just before the closing
</body>tag. Save and reload your site. The widget loads on its own. - WordPress: Install a headers-and-footers plugin (for example "WPCode" or "Insert Headers and Footers"), or open Appearance then Theme File Editor. Paste the code into the Footer, or just before
</body>. Save. Reload your site and the widget appears on every page. On WordPress.com, plugins and custom code need the Business plan or higher. Self-hosted WordPress has no such limit. - Wix: In your Wix dashboard, open Settings, then Custom Code (under Development & integrations, or under Advanced on older dashboards). Add Custom Code, paste the code, and set it to load on All pages, in the Body - end. Apply, then publish your Wix site. Wix only runs custom code on a Premium plan with a connected domain.
- Squarespace: Open Code Injection: on newer Squarespace sites it is in the Pages panel under Custom code; on older ones it is under Settings, then Advanced. Paste the code into the Footer box. Save. Your live site now loads the widget on every page. Code Injection is not on the Squarespace Personal or Basic plan. It needs Business, Core or higher.
- Shopify: In Shopify admin, open Online Store, then Themes, then the three-dot menu and Edit code. Open
theme.liquidand paste the code, just before</body>. Save. The widget shows across your storefront. - Webflow: In Webflow, open Site settings, then Custom code. Paste the code into the Footer code box. Save, then publish your site. Webflow only publishes custom code on a paid site plan.
- Framer: In your Framer project, open Site settings, then General, then Custom Code. Paste the code into the End of
<body>tag box. Save, then publish your site. Framer runs custom code on its paid site plans. - Google Sites: Google Sites blocks site-wide scripts, so open the Install tab, switch Embed type to Script embed under Advanced options, and copy that snippet. On your page choose Insert, then Embed, then Embed code, and paste the snippet. Publish. The AI agent appears inline on that page. The floating launcher cannot run site-wide on Google Sites. The Script embed option is the supported route.
- GoDaddy: In the GoDaddy website builder, open Settings, then Site-wide code. Paste the code into the box for code added to every page, and save. Publish your site. If your GoDaddy plan has no Site-wide code setting, it cannot run the floating widget on every page. A WordPress or HTML site hosted at GoDaddy follows those guides instead.
- Weebly: In the Weebly editor, open Settings, then SEO. Paste the code into the Footer Code box. Save, then publish your site.
- Jimdo: In Jimdo Creator, open Settings, then Edit Head. Paste the code into the box and save. Reload your site. The widget appears on every page. Edit Head is on Jimdo Creator's paid plans. The newer Jimdo website builder has no site-wide code setting, so it cannot run the floating widget.
- Carrd: In the Carrd editor, add an Embed element and set its Type to Code. Paste the code, set Style to Hidden and Location to Body End. Save and publish your site. Carrd's Embed element needs a Pro Standard plan or higher.
- HubSpot CMS: In HubSpot, open Settings, then Content, then Pages, and pick your domain. On the Templates tab, paste the code into Site footer HTML. Save. The widget loads on every page of that domain.
- Ghost: In Ghost Admin, open Settings, then Code injection. Paste the code into the Site footer box. Save. The widget shows on every page and post.
- Duda: In the Duda editor, open Settings, then Head HTML. Paste the code into the box. Save, then republish your site.
- Hostinger: In the Hostinger Website Builder, open Website settings, then Integrations. Paste the code into the Custom code box and save. Publish your site. A WordPress site hosted at Hostinger follows the WordPress guide instead.
- Strikingly: In the Strikingly editor, open Settings, then Advanced, then Custom Code. Paste the code into the Site-wide footer code box. Save, then publish your site. Site-wide custom code is on Strikingly's Pro and VIP plans.
- Notion (with Super): In your Super dashboard, open your site, then Code. Paste the code into the Body box. Save. Super adds it to every page of your Notion site. A plain public Notion page cannot run scripts. You need a Notion site host that allows custom code, such as Super.
- Bubble: In the Bubble editor, open Settings, then SEO / metatags. Paste the code into Script in the body. Deploy your app to Live.
- BigCommerce: In BigCommerce, open Storefront, then Script Manager, then Create a Script. Set Location to Footer and Pages to All pages, choose Script as the type, and paste the code. Save. The widget shows across your store.
- Joomla: In Joomla admin, open System, then Site Templates, and pick your template's files. Open
index.phpand paste the code, just before</body>. Save. Reload your site and the widget appears on every page. A template update can overwrite this edit. A child template, or a custom code extension, keeps it safe. - Drupal: In your theme's templates folder, open
html.html.twig(copy it from your base theme if it is not there). Paste the code, just before</body>. Save, then clear the Drupal cache (Configuration, then Performance, then Clear all caches). - Next.js: Open
app/layout.tsx(App Router) orpages/_document.tsx(Pages Router). Add it withnext/script: <Script src="..." strategy="afterInteractive" /> with the same src and data- attributes as the code. Deploy. The widget loads on every page. - React (Vite or Create React App): Open
index.html(in the project root for Vite, in public/ for Create React App). Paste the code, just before</body>. Build and deploy. The widget loads on every page. - Vercel: Open your project's root HTML or layout (for example
index.html,app/layout.tsx, orpages/_document.tsx). Paste the code, just before</body>. Commit and deploy. The widget loads on every page. - Netlify: In Netlify, open your site, then Site configuration, then Build & deploy, then Post processing. Under Snippet injection, add a snippet before
</body>and paste the code. Save. Netlify adds it on the next deploy. - gamma.site: Open your Gamma site and its publish or site settings. Add the code wherever Gamma allows custom embed code. Publish your site. If your Gamma plan does not allow custom code, connect a custom domain and add the code on that host instead.
If someone else looks after your website, you can email them the snippet and the steps for your site builder: type their address under Or send it to your developer on the Go live page, or in step 3 of the Ready to go live window in Backstage, and choose Email this to my developer. The email carries the steps for the builder you picked in the guide. The email comes from Dante AI in your name (for example "Ana Lopez via Dante AI"), asks them to add your AI agent to your site, and comes with the code to copy. It is signed with your name, and if they reply, the reply comes straight to you. If your name looks like a company or a help desk (for example it has "Support" or a brand in it), the email comes from plain "Dante AI" and your name appears only in the sign-off. To send it you need edit rights on the agent and a confirmed email address (open the link in the email we sent when you signed up). There is a limit on how many can be sent each hour and each day.
The official WordPress plugin
If you run WordPress you can use the official Dante AI Echo plugin instead of pasting the snippet. It connects with an API key rather than code, so you never touch your theme files.
In the WordPress plugin directory, search for Dante AI Echo. The older plugin called just Dante AI is for the earlier platform and does not work with this key.
Open Integrations in your dashboard and generate a WordPress API key, then paste it into the plugin settings. The key is available on every plan, including Free, and it is scoped to the read-only endpoints the plugin needs, so it cannot change anything in your workspace.
Is it live? Check the status card
The Install tab shows a Live status card right above the snippet so you never have to guess whether the paste worked. It updates the first time a real visitor loads your page with the snippet on it.
- Not detected yet. We haven't seen your AI agent load on a live site. Paste the snippet on your site, open the page, then click Check again (or reload the Install tab).
- Your AI agent is live. The snippet is working on your website. Nothing else to do.
- Detected on a sandbox site. We saw your AI agent load on a preview or sandbox host rather than your real website. Embed it on your real site to go live for your visitors.
Check again re-checks on demand, so you can paste the snippet, switch back to this tab, and confirm it went live without a full page reload.
Updating the snippet
You don't need to update the snippet when you change the agent's appearance, knowledge, or behaviour. Those updates apply automatically the next time a visitor opens the chat. The only times you'll repaste the snippet are after rotating the widget key (Security settings) or switching to a custom domain (Custom domains).
The snippet always loads the widget from
agents.dante-ai.com, whichever Dante address you
opened the dashboard on. If an older snippet on your site points
at www.dante-ai.com/embed.js, copy the snippet again
from Publish and replace it.
On phones the chat opens full screen
When a visitor on a phone taps your launcher, the chat now takes over the whole screen, the way a messaging app does, instead of opening as a small floating card. Nothing to configure and nothing to repaste: it is part of the snippet you already have.
A few things that follow from it, so they don't surprise you when you test on your own phone:
- A close button appears in the top right of the chat header, next to the menu. That is how a visitor gets back to your page, so the launcher button hides itself while the chat is open rather than sitting on top of the message box.
- Your page stops scrolling behind the chat while it is open, and returns to exactly where the visitor left off when they close it.
- The chat respects the notch and the home indicator on phones that have them, and the strips around them are painted in the background colour you picked in Styling.
Tablets and desktops are unchanged: there the chat still opens as the floating panel in the bottom corner, and the launcher stays visible as the way to close it.
Keyboard and screen readers
The chat on your site works without a mouse. When it opens, the cursor lands in the message box, so a visitor can start typing straight away. Pressing Escape closes the chat (if the emoji picker is open, the first Escape closes the picker) and puts the visitor back on the launcher button they opened it from. Screen readers announce the chat as a dialog named after your agent, for example "Northside Studio chat". On phones, where the chat covers the whole screen, the Tab key stays inside the chat until it is closed.
If you turned on voice input, the microphone button shows in
the chat on your website exactly when it shows in the preview
on the Publish page: in browsers that support speech to text,
on an https page. The embed snippet already gives the chat
permission to use the microphone, so there is nothing extra to
paste. If you built your own iframe instead of using the
snippet, add allow="microphone" to it, or the
button stays hidden. Visitors whose browser cannot take
dictation simply type.
The chat keeps its place when visitors change pages
When a visitor is mid-conversation and clicks through to another page on your site, or reloads the page, the chat now carries on where they left off. They see the same messages, and your AI agent continues the same conversation instead of starting a new one. Nothing to configure and nothing to repaste.
- It lasts as long as the visitor keeps that browser tab open. Closing the tab, or opening your site in a new tab, starts a fresh conversation with the usual greeting.
- A visitor who signed in on your site keeps their own thread, and it is not shown to the next person on the same browser after they sign out.
- If a visitor's browser blocks site storage (some private browsing modes do), the chat still works. It just starts fresh on each page.
- The preview in your dashboard always starts fresh, so testing there never mixes with a real visitor's conversation.
Widget not showing up on your site?
The most common cause is a domain that isn't on your allow list. If your widget tries to load from a site that isn't in Allowed domains, it is blocked on purpose so nobody else can run your snippet, and the launcher simply won't appear for visitors.
We make this visible for you. When you go live from the builder,
your AI agent is locked to the site you gave it. The
Go live, Install tab says so at the top ("Only
your-site.com can show your AI agent"), and if the
widget was refused somewhere else you'll see "Blocked on
other-site.com 2 minutes ago. Allow this site?" with
an Allow button. One click adds that site and the
widget shows there on the next page load. You can also type a site
into Add another site before you paste the code
there. The builder's install check and the go-live window show the
same line, and you can ask Backstage "why isn't my widget showing?".
?dante-debug=1 to your site's URL to see a small
owner-only message that names the exact domain to add.
Optimisation and caching plugins can break the widget
If the snippet is pasted correctly but the launcher still never
appears, the usual culprit is a performance plugin on your site.
WordPress optimisation and caching plugins "combine", "minify",
"defer", or "delay" JavaScript to speed up page loads. When one of
those features swallows our async loader, embed.js
either never runs or runs out of order, and the widget silently
fails to mount. Nothing in your Dante settings is wrong, the loader
just never got a chance to run.
Symptom. The launcher does not appear on your live site (often only after you installed or enabled a speed plugin), but it works in an incognito window with caching off, or on a copy of the site that does not have the plugin.
Fix. Tell the plugin to leave our loader alone. Exclude the Dante script from JS combine, minify, defer, and delay. The script URL to exclude is:
https://agents.dante-ai.com/embed.js
Most plugins accept a partial match, so just embed.js
or dante on its own works too. Here is where each of
the common plugins keeps that setting:
-
SiteGround Optimizer (SG Optimizer). WordPress
admin, SiteGround Optimizer, Frontend, JavaScript. In the
Combine JavaScript Files and Minify
JavaScript Files options use the "Exclude from JS
combination" / "Exclude from minification" box and add
embed.js. If Defer Render-blocking JavaScript is on, addembed.jsto its exclusion list as well. -
WP Rocket. Settings, WP Rocket, File
Optimization. Add
embed.jsto Excluded JavaScript Files. Then open Delay JavaScript Execution on the same page and addembed.jsto its excluded list (move it out of delay) so the loader is not held back until a visitor interacts with the page. -
Autoptimize. Settings, Autoptimize, JavaScript
Options. Add
embed.jsto Exclude scripts from Autoptimize, which is a comma-separated list, so "Aggregate JS-files" leaves the loader untouched. -
W3 Total Cache (W3TC). Performance, Minify, JS.
Under Minify, add
embed.jsto the Never minify the following JS files list (or turn JS minify off). If you use its defer / non-blocking option, exclude the script there too.
After changing any of these, purge the plugin's cache and reload
your page in a private window. The launcher should return within a
second. The same approach works for any other combine / minify /
defer / delay plugin (LiteSpeed Cache, Perfmatters, Hummingbird and
similar): find its JavaScript exclusion list and add
embed.js.
Widget appears but won't answer
Symptom. The launcher loads and opens and the welcome message shows, but every visitor message gets back "Sorry, this AI agent isn't available at the moment. Please contact the business directly for help." instead of a real reply.
Cause. The widget itself is healthy, only the reply step is paused. That wording means the workspace balance reached zero: replies cost credits, and when the monthly allowance plus any earned or purchased credits run out, the AI agent stops generating answers until the next reset or a top-up.
Fix. Confirm it first. Open Billing and read the balance. If it really is at zero you can add the Extra Credits add-on for an immediate top-up, switch the agent to a 1-credit model so each reply costs less, or upgrade the plan for a bigger monthly allowance. See Understanding credits for the full breakdown.
Widget says the agent hit its monthly limit
Symptom. Visitor messages come back as "This agent has reached its monthly credit limit." while the workspace balance is still healthy.
Cause. This is a separate, per-agent ceiling that somebody on your team set, not a billing state. Each AI agent has its own Monthly credit cap, and once this agent's widget replies have used that many credits it refuses new messages until the window resets. The workspace can be full of credits and this agent will still be paused.
If human handover is on for this agent, a visitor who asks for a person, or presses the handover button, still reaches your team while the cap is hit. Only the AI answers are paused.
Fix. Open Agent settings, Security and change Monthly credit cap for this AI agent. Raise it, or set it to 0 to remove the ceiling entirely. Buying credits does not lift this cap. See Security settings for what else lives on that page.
Widget briefly will not open on a very busy network
What it does. The chat widget limits how fast one network address and one AI agent can open new chats. This keeps a burst of automated traffic, such as a script hammering your site, from running up your bill.
Symptom. On a very busy shared network, such as a large office, school or public WiFi where many people sit behind the same address, visitors may briefly see the widget not open. This clears on its own within a minute and does not affect the billing balance shown in Billing.
Trouble pasting? We're here.
If the launcher doesn't appear after pasting, send us your website URL and we'll tell you exactly where to put it.