REST API: custom domains
Attach, verify, and route a custom domain for an agent's public surfaces.
A custom domain lets an agent's public-facing surface, such as its Help Center, appear under your own hostname instead of an AgentStack subdomain. List an agent's domains, then add one with the hostname you control. Adding a domain does not make it live: you must complete DNS and SSL verification before it serves traffic.
After you add a domain, configure the DNS records AgentStack requires at your registrar or DNS provider, then call POST /custom-domains/{domainId}/verify to re-check status. Verification is asynchronous on AgentStack's side too — DNS propagation and certificate issuance take time, so poll verification with bounded backoff rather than a tight loop, and do not assume a single verify call finishing means traffic is already routing.
PATCH /custom-domains/{domainId}/surface changes which public surface, such as the Help Center or the embed, a verified domain routes to. Only change the surface after confirming the domain is verified, since routing an unverified domain does not make it reachable.
Removing a custom domain is a routing change with a customer-facing impact: any link or bookmark using that hostname stops resolving to the agent's surface immediately. Confirm the domain is no longer referenced anywhere public before you delete it.