Public link
Share your site's assistant at a public, no-login URL. Pick which agent it serves and rotate the link if it leaks.
The public link puts one of your site's agents at a URL anyone can open and chat with: no iAdvize account, no dashboard access. Use it to send a prospect a working assistant, or to give a stakeholder a live demo without inviting them to your organization.
The link belongs to the site, not to a single agent: each site has one public link (https://www.iadvize.ninja/s/<public-key>) that serves the site's default public agent. It's a plain, stripped-down chat page, nothing else. To put the assistant on your own storefront instead of a standalone page, use the web tag; the public-access toggle here doesn't gate the tag.
Turn on the public link
Everything happens on one page: the site's Settings → Public access. Pick the agent, flip the switch, copy the link.
Open the site and go to Settings → Public access. Choose the agent the link should serve from the Default agent select. It lists only this site's agents that have a published (champion) version. If the site has none, the page tells you so, and you promote a champion first before you can go any further.
Turn on Enable public access. The switch stays disabled until you've picked a default agent (you can't turn the link on without one). Only the agent you selected answers; switch to a different one anytime by picking another from the same select.
The public URL appears once access is on. Copy it with the copy button and share it however you'd share any URL: email, chat, a demo deck.
If a link has leaked or you just want a clean one, use Rotate on the Public access page. This is different from turning access off: rotating immediately issues a new link and the old one stops working right away, so anyone who still has it gets a dead link and needs the new one. Turning access off instead pauses the link without discarding the key; turning it back on reuses the same link.
What visitors get
- Chat only. The page reuses the same chat component as the dashboard playground, with no dashboard chrome, no conversation history, no version picker.
- The agent's identity, shown at the right moment. Before the first message, the served agent's avatar and display name (set on its Public identity card) show above the welcome message (or a generic assistant icon and label if neither is set), but only when a welcome message is configured for the visitor's language. If not, the compact chat header keeps showing the identity throughout instead. Once the visitor starts typing or the conversation has a message, the identity moves into (or stays in) the header. The site's own logo never appears in the chat.
- Friendly status messages, never raw tool calls. While the assistant is working (searching the catalog, comparing products, thinking through a reply), visitors see a short, plain-language status instead, like "Looking for the best products for you…" or "Thinking…", shown only while that step is in progress, and, when the assistant loads a conditional instruction block you gave an indicator message, that phrase in the visitor's own language. Once it finishes, only the result appears (a product carousel, comparison, detail card, or clarifying question), or nothing at all if there's nothing to show. This is fixed for the public link: there's no setting to show the raw tool name, its JSON, or the assistant's reasoning here. You can preview this exact display from the dashboard using the User view option in the playground's configuration panel.
- The current champion, always. The link serves the default agent's champion version. If you promote a new champion, the link starts answering with the new version immediately, so you don't need to reshare anything. A draft or candidate version is never reachable this way.
- Every linked connector works, same as the playground. Whatever connectors are linked to the champion version (Shopify, Custom, or any other e-commerce connector) run on the public link exactly like they do in the playground. There's no connector-type restriction: catalog search, cart/policy tools, and any Custom connector's tools all work the same way here as they do for your own team testing the agent.
- Visitors can rate any response. Every assistant message has a thumbs-up/thumbs-down control that opens a short dialog (an optional issue category for a thumbs-down, an optional comment either way) rather than submitting instantly. Submitting shows a one-line notice that the feedback and conversation may be reviewed internally, shown only on this surface. See Rate a message for the full behavior.
- Not indexed. The page and its API route are excluded from search engines (
robots.txtand anoindextag), so sharing the link is the only way anyone finds it.
Rate-limit protection
The public link and the embedded web tag share the same chat endpoint, and it's protected against abuse by two layers, both managed by iAdvize. There's nothing to configure on your side:
- A per-visitor limit: 15 requests per 10 seconds. Tuned to stop a single abusive source (someone hammering the endpoint from one place) without ever affecting normal shopper traffic, even for a large merchant whose traffic naturally comes from many different visitors.
- A per-organization ceiling: 1,200 requests per minute. Set deliberately high so it never throttles legitimate usage. It only trips on an unusual, distributed flood across many sources at once.
Regular traffic, however busy your storefront gets, won't come close to either.
The link itself is the access control
Anyone who has the link can chat with the assistant: there's no password or login on top of it. Don't share it anywhere public you wouldn't want a stranger to find (a public GitHub repo, an indexed forum post). If a link gets out, rotate the key.
When the link stops resolving
The public link returns a not-found page (rather than an error) whenever it can't resolve to a live agent. This is by design, so a stale or guessed link never leaks anything:
- Public access is turned off for the site, or the key has been rotated.
- The default agent was deleted, or detached from the site. Pick another default agent on the Public access page to bring the link back (the select only offers agents still on the site with a champion version).
- The default agent no longer has a champion version.
Public-link conversations show up in Conversations on the Hosted channel. You can review the transcript there like any other conversation.
Web tag performance
What the web tag costs a storefront page: the size budget we commit to, the current measurement, what we enforce on every change, and how to measure it live on your own storefront.
Conversations
Review chat transcripts, filter by the AI judge's labels, work through the Needs review queue, rate individual assistant messages, and delete a conversation when you need to.