What do I need to connect a domain?
Custom domains are a paid feature. Check Pricing for current plans and the Domain panel for your account allowance. If your main website should stay where it is, you can use a separate subdomain for the agent.
The root domain, www address, and other subdomains are separate addresses. Tell the Builder whether you want www as well when connecting a root domain.
- A domain you own and access to its DNS settings.
- The exact address you want, such as example.com or assistant.example.com.
- Available custom domain capacity on your Agentplace plan.
- A published agent before the domain can serve visitors.
How do I connect my domain?
Use the exact records from your connection. The ownership TXT record proves control of the domain. Routing records direct visitors to the agent. If the panel offers CNAME or A/AAAA as alternatives, use one routing option together with the ownership record.
DNS changes can take time to become visible. The Builder can follow the setup status with you. You do not need to obtain or install an HTTPS certificate separately.
- Open the agent workspace and tell the Builder which exact domain or subdomain to connect. You can also use the Domain panel.
- Copy the DNS records shown for your connection, including each record’s type, name, and value.
- Add those records at the service that manages your domain’s DNS.
- Follow the connection status while Agentplace verifies ownership, checks routing, and sets up HTTPS.
- Publish the agent if it is still a draft. Once the domain is active, open its HTTPS address and test it with the intended visitor access.
Example domain request
Connect assistant.example.com to this agent. Keep my existing website at example.com. Show me which DNS records to add and help me check when the agent is available.
Why is my domain not live yet?
If you still see the old website, check that you opened the exact address you connected and that its routing records point to Agentplace. If HTTPS setup fails, follow the reported cause rather than repeatedly changing unrelated DNS records.
| Setup stage | What it means | What to do |
|---|---|---|
| Ownership verification | Agentplace has not yet confirmed the ownership record. | Check the TXT name and value against the current setup instructions. |
| Routing verification | Ownership is confirmed, but routing records are not ready. | Check the selected DNS routing records and allow time for the changes to appear. |
| HTTPS setup | Agentplace is preparing or validating the certificate. | Wait for setup to finish and follow any specific error shown. |
| Waiting for publication | The agent still needs to be published before it can serve visitors. | Publish the agent. If the status says a final recheck is in progress, wait for that check. |
| Active | The domain is serving the agent. | Open the HTTPS address and test a customer task. |
| Failed | One of the setup checks did not complete. | Ask the Builder to explain the reported cause and help retry after addressing it. |
Does a custom domain change access to the agent?
Your custom domain uses the same publishing access rules as the agent. Public, Restricted, Private, and Require sign-in still apply. Connecting a domain does not make a private agent public or remove a sign-in requirement.
You can prepare the domain while the agent is a draft. Finishing DNS setup does not publish the agent for you.
How do I disconnect or change the domain?
Use the Domain panel to review and confirm disconnection. Disconnecting releases the address from its Agentplace binding. If the address should return to another website, update its DNS routing at your provider as well.
To use a different address, connect and verify that address through the domain setup flow. Review where visitors should go before removing a working domain.