connect-domainlisted

# Connect a Custom Domain A site deployed on simple-host is already live at `https://sites.simple-host.app/<handle>/<site>/`. This skill connects the user's **own domain** — a subdomain (e.g. `recipes.brand.com`) or an apex (e.g. `brand.com`) — so the site is served from it over HTTPS. A domain is what adds **sign-in** to saves. Visitors sign in with Google or an emailed code only on a site's own domain; on the shared host every site is the same origin, so a sign-in there could never be private to one site — pages there save freely, and anyone can change that data. This is the reason most people connect one. **This is agent-driven.** You do every API call and compute the exact DNS record. Then either **add that record yourself** if you have DNS access for the domain (a provider MCP/API — see step 3b; ask permission first), or hand the human the single record to paste. Buying a domain (when they have none) and — absent your own DNS access — pasting the record are the only human steps. ## When to use this - The user asks to use their own domain / brand for a site. - The user wants saves from a page (a guestbook, RSVP, poll, counter) to be per-person or protected by sign-in. The `website-deploy` skill sends you here for that. ## Service - Base URL: `https://simple-host.app` - Auth header: `X-API-Key: <api_key>` (the key from deploying the site) - One domain per site; a domain can be connected to only one site. ## The flow ### 1. Confirm the site exists and pick the do