Skip to main content
Everything in the Agents and Campaign sections assumes a phone call. OpenMic also runs the same agents inside a web browser over WebRTC — a visitor clicks a button on your site and starts talking, with no phone number, no carrier, and no telephony setup.
The agent is the same object either way. A single agent you have already built and tested can take phone calls and browser calls at the same time — same prompt, same voice, same tools, same knowledge base, same webhooks.

​
Three ways to get an agent into a browser

Voice widget

A drop-in voice call button for your website. One script tag.

Chat widget

A floating text-chat panel backed by the same agent. One script tag.

Share link

A public URL anyone can open and talk to your agent. Zero integration.

​
Which one should I use?

Just want to show someone your agent? Use a share link. It takes one click in the dashboard and requires no code at all.

​
Before you start

Both widgets are client-side embeds, so they authenticate with your organization’s public API key — never your secret key.
Never paste a secret API key (omic_...) into a web page. Anything in a widget snippet is visible to every visitor. Client-side embeds use the public key (omic_pub_...) only. See Public API key.
You will need:
1

An agent

Any agent from your dashboard. Copy its UID — the widgets identify agents by UID, not by name or numeric ID.
2

Your public API key

Found in the dashboard, or via GET /api-keys/public-key. It starts with omic_pub_. See Public API key.
3

An HTTPS page

Browsers only grant microphone access on secure origins. https:// and http://localhost both count as secure — but note the voice widget has a known localhost limitation.
The dashboard generates ready-to-paste snippets for both widgets, filled in with the selected agent’s UID and your public key. Open any agent and choose the Widget tab.