Share links
The public link that lets anyone talk to an agent without an account, and the caps that keep it safe to hand out.
A share link is an unguessable URL that lets anyone talk to your agent in a browser, with no account and no sign-in. It exposes the agent without exposing anything else in the workspace.
| Exposed | Not exposed |
|---|---|
| The agent's name, description and workspace name | The prompt, tools, variables or knowledge base |
| A conversation with the agent | Transcripts, calls or analytics |
| Any other agent in the workspace |
Creating a link
In the agent's Share section, switch sharing on. The platform mints a URL from the agent's slug plus a random suffix and shows the full link to copy.
Minting and revoking is a workspace-member action: a per-agent collaborator cannot make an agent publicly reachable.
Which version a visitor hears
The page runs the agent's published version. A draft edit does not reach the link until you publish.
If the agent has never been published, the newest draft answers instead, so a brand-new agent is demonstrable before its first publish.
Talking to the agent
Visitors talk to the agent in their browser. If the microphone is blocked or unavailable, the page falls back to a typed conversation.
The page asks search engines not to index it, but that is a request rather than a boundary. Treat the URL itself as the access control.
Limits on the public surface
Four caps are configured in the Share section.
| Cap | Default | Range |
|---|---|---|
| Longest call | 3 minutes | Up to 60 minutes. Set 0 for no cap. |
| Turns per conversation | 30 | Up to 500. Set 0 for no cap. |
| Starts per address, per window | 10 | 1 to 1000 |
| Rate-limit window | 10 minutes | 1 minute to 1 day |
On a voice call
A voice call runs under the two call caps above. On an agent whose Share panel has never been touched, the call ends at whichever cap lands first.
Defaults, untouched: the call ends after 3 minutes or 30 turns
Longest call set to 0: the call runs as long as the visitor keeps talkingRaise either value if three minutes is too short for what you are demonstrating.
Turning a cap off
Setting a cap to 0 removes that limit. Only do this when you know who holds the link.
On a typed conversation
The turn cap limits how many messages a visitor may send. The request throttle is derived from the two rate-limit settings and counted per share link, so a busy demonstration on one agent does not throttle another.
Guards you cannot configure
Three limits apply regardless of what you set above.
- Silence reap. A silent call is reaped after ten minutes. The timer resets on any speech from either side, so it catches abandoned tabs, not active conversations. This is the only bound on a call whose length cap is set to 0.
- Shared start limit. Ten starts per visitor address every ten minutes, fixed platform-wide and shared across every share link. A burst on one link consumes the allowance for the rest.
- Bot check. Runs on every start. Traffic identified as automated is refused before the agent is reached.
Revoking a link
Switch sharing off. The link stops working immediately.
Switching sharing back on mints a fresh URL rather than restoring the old one, so a leaked address stays dead. Archiving the agent also takes its share page offline. See Agent lifecycle.
Share link or website widget
| Share link | Website widget | |
|---|---|---|
| Where it runs | A page hosted for you | Your own website |
| Who it is for | One person you want to hear the agent | Your visitors, at scale |
| Access control | Possession of the URL | A publishable key with an allowed-sites list |
| Which version answers | Published | Published |
| Rate limit | Fixed: ten starts per address every ten minutes, shared across all links | Configured per key |