Skip to main content
Two different things are called “publishing”, and confusing them wastes an afternoon: Deploying is covered in Build an AI agent. This page is about the second one.

Plan limits, before you build

Both limits are enforced at the moment you publish, not while you build. It is entirely normal to design four agents on Free and discover the cap only when you deploy the second — so check the numbers first. Published agents — deployed agents live in your workspace at any one time: On Free, the message reads “Your Free plan can publish 1 agent or automation at a time. Drafts are always unlimited. Upgrade to Starter to publish more.” Drafting really is unlimited on every plan. Public agent UIs — chat assistants exposed on the web: On Free the Public UIs button is not shown at all: “Public Agent UIs are available on the Starter plan and above.”

Publish a public UI

1

Open Public UIs

Select Public UIs on the Agent Builder page. The Public Agent UIs screen shows a live preview beside the editor and a badge counting how many of your allowance you have used.
2

Choose an agent

Under Choose an agent, select Enable on the one you want. Only deployed agents that are set to de-identified and use safe tools can be made public; anything ineligible says why on its row.
3

Set the address

Your link appears under Your link. On Team you can set your own address; on lower plans the address is generated and Regenerate issues a new random one. Custom links are a Team feature.
4

Write what visitors see

Under Content, set the Title, Headline, Welcome message, Input placeholder, up to six Suggested prompts and a Footer note. Under Branding, set an accent colour, a Theme and a logo.
5

Set the abuse caps

Under Access & limits, keep Live on, and set Messages / minute per visitor, Daily messages per visitor and a Monthly run cap. Turn on Require email to chat if you want visitors identified before they can ask anything — disposable addresses are blocked.
6

Save changes

Select Save changes. The preview and the live page both update.
Every visitor message on a public UI spends your agent credits, and the page is reachable by anyone who has the link. Set the Monthly run cap before you share the address — with it blank, the only thing limiting spend is your balance.

Put it on your website

The Add to your website card gives you what your plan allows: a hosted link on Starter, a widget snippet on Essential, and on Team the full widget options (Floating button or Inline on the page, its position and its Button text) plus the raw <iframe>. Paste the snippet into your site’s HTML. See Embeds. A public UI can also live on your own domain — assistant.yourclinic.com — via Custom domains.

Take one offline

Live switches the page off without losing the configuration. Take offline & remove deletes the public UI entirely: the link stops working immediately, and a new one later gets a new address.

Check it worked

  • The counter at the top of Public Agent UIs has gone up.
  • Opening your link in a private browser window shows the branded chat, with your headline and suggested prompts.
  • A message sent from that window appears on the Runs page and debits credits.

If something goes wrong

You are on Free. Public agent UIs start at Starter — see Change your plan.
You have reached your plan’s published-agent cap (Free 1, Starter 5). Take an agent offline, or move up a plan. Nothing you have drafted is lost.
Only deployed agents can be made public, and only ones set to de-identified that use safe tools. Deploy it first, and check the reason shown on its row.
Custom addresses are a Team feature. On Starter and Essential use the generated link, or Regenerate for a different one.
Lower Messages / minute per visitor and Daily messages per visitor, set a Monthly run cap, and turn on Require email to chat. Switching Live off stops it immediately.

Build an AI agent

Drafting, triggers, and deploying inside your workspace.

Agent credits

What public conversations cost you.

Custom domains

Serve the assistant from your own address.

Change your plan

Raise the publishing and public-UI limits.