Docs
App addresses and your own domain
Every app is reachable over HTTPS the moment it is ready. Adding your own domain takes two DNS records – and works the same whether your agent does it or you do.
The address every app gets
https://<app>-<account>.build.agenthotel.org
For example https://shop-alice.build.agenthotel.org. You can pick another name under
build.agenthotel.org with the host setting, as long as it ends in
-<account>, so nobody can take a name that looks like yours.
Your own domain, two ways
Through your agent
- Ask: “Add shop.example.com to the shop app.” The agent calls
add_domainand tells you two DNS records. - Create the records at your DNS provider.
- Say “verify it.” The agent calls
verify_domain.
In the portal
- Apps → your app → Domains, type the domain, Add domain.
- Copy the two records to your DNS provider.
- Press Verify.
The two records
| Type | Name | Value | Why |
|---|---|---|---|
| TXT | _agentbuild.shop.example.com | agentbuild-verify=… | Proves that you control the domain |
| CNAME | shop.example.com | shop-alice.build.agenthotel.org | Sends visitors to your app |
A root domain such as example.com cannot have a CNAME; you get A records
instead (one per address shown).
Cloudflare: set the record to “DNS only” (grey cloud) so the certificate can be issued.
After verification
- The certificate is issued automatically once the domain points here – usually within a minute or two.
app_statusand the portal show when it is ready. - A verified domain belongs to that app: no other account can claim it.
- Up to 10 domains per app.
remove_domainstops serving one. - DNS changes can take a few minutes to spread. If verification fails, wait and try again.