Verify your domain
Two ways to prove ownership — a DNS record, or just installing the widget.
A verified domain proves where your agent is allowed to answer. Until a domain is verified, the widget stays silent on it.
Claim it#
- Open Library · Domains.
- Type the host in the Domain field —
support.acme.com, not a full URL. - Press Add domain.
It appears as Pending, with two ways to prove ownership. You only need one.
Option 1 — add a DNS record#
Bidirection shows a token that looks like bench-verify= followed by a long hex string. Add it as a TXT record on that domain, then press Verify.
The record is accepted at either the domain itself or at _bench-verify. in front of it — whichever your DNS provider makes easier.
If it still fails after 15–30 minutes, the record is usually at the wrong host name or has a typo. Compare it character for character with the token in the console.
Option 2 — just install the widget#
No DNS access? Paste the agent's script tag on the domain and press Verify. Bidirection fetches the page, finds your key, and verifies on the spot. It also verifies by itself the first time a real visitor loads the page.
See Install the script.
www and the bare domain#
Verifying either spelling authorizes both. You do not need two claims for acme.com and www.acme.com. This applies to the www pair only — a subdomain like app.acme.com is its own claim.
Removing a domain#
Remove drops the claim from your workspace. It does not touch your DNS. Bidirection lists the consequences before you confirm: the widget stops answering there immediately, SSO routed by that domain stops, and any agent attached to it detaches.
You can claim it again later, but verification starts over.
Next#
Verifying says the host is yours. Deciding which agent answers there is a separate step — see Attach domains to agents.