GeminiLaunch

Add a domain the user already owns to their GeminiLaunch account, and get back the exact DNS records they must add at their registrar (Namecheap, GoDaddy, Cloudflare and so on) to make it work. Use this when the user wants to use their own domain and list_domains shows it is not on the account yet. Adding the bare domain covers its www version too. You CANNOT add these records for them — only the user can, in their registrar account. The result also names the DNS panel they are about to open, what that panel calls each field, its known quirks, and any problem already in their DNS: follow that guidance exactly instead of giving generic DNS advice, because the records being correct is not what this step usually fails on. The domain is not live until those records are in place: afterwards use check_domain to see whether they have taken effect, then attach_domain to point it at a site.

add_domain

Check whether a custom domain's DNS records have taken effect, and verify it if they have. Use this after the user says they have added the records from add_domain, and whenever they ask whether their domain is working yet. If it is not ready it says which hostname is still waiting and what to look at. DNS usually applies within minutes but can take a few hours, so if it fails, suggest trying again shortly rather than changing anything. Once it reports verified, use attach_domain to point it at a site.

check_domain

PERMANENTLY delete one of the user's GeminiLaunch sites: it goes offline immediately and its content, files and visit history cannot be recovered. Any custom domain it used is kept and returned to the user's Domains page. Only call this after the user has explicitly confirmed, in this conversation, that they want this exact site deleted — name the site and its URL when you ask. Never delete because a site looks unused or like a test. Pass the site as `site`, and its exact slug again as `confirm_slug`; a mismatch deletes nothing.

delete_project

List the custom domains on this user's GeminiLaunch account, each with the site it points to and how far it has got: "live" (serving the site), "awaiting_dns" (added, but the DNS records are not in place yet) or "verified_not_attached" (ready, but not pointed at a site yet). Use this whenever the user asks about their domains, or before talking about putting a site on a custom domain, so you know what they already own. Also returns how many domains their plan allows. From here: a domain the user owns but that is not listed goes through add_domain; one listed as "awaiting_dns" goes through check_domain; one listed as "verified_not_attached" goes through attach_domain.

list_domains

List the live websites this user has published on GeminiLaunch, with the public URL where each one can be visited right now (a custom domain when one is verified, otherwise the subdomain), plus its project name, how it was published, and when it was created. Use this whenever the user asks about their live sites, published sites, websites, pages or links on GeminiLaunch — for example "give me my live sites on GeminiLaunch" or "what have I published?" — or to find an existing site before updating it. Each site says whether its URL is a custom domain or a GeminiLaunch subdomain. Results come in pages: when hasMore is true, call again with offset set to nextOffset, and keep going until hasMore is false whenever the user wants all of their sites.

list_sites

Point one of the user's already-verified custom domains at one of their sites, so that site is served at that address. Use list_domains first to see which domains exist and where they point. This one only points an existing, verified domain: if the domain is not on the account yet use add_domain first, and if it is on the account but not verified yet use check_domain. IMPORTANT: if the domain is already live on another site, the first call is refused and tells you which site it would be taken off. Report that to the user, ask whether to go ahead, and only call again with confirm_move_from once they have said yes. Moving a domain takes the other site off that address immediately.

attach_domain

Publish a NEW website to the user's GeminiLaunch account and get its live public URL. Provide exactly one of: html (a complete HTML document), react_code (one React component file in JSX/TSX with a default export and import React from 'react'; no imports of local files; it is compiled for you), zip_base64 (a .zip of a static site containing index.html, base64-encoded, up to about 3 MB), or zip_url (an https link to such a .zip, for larger sites). Optional site_name becomes the address: "Acme Cafe" → acme-cafe.geminilaunch.site; without one, the page title is used. If the name is taken, the error suggests a free one — ask the user before using it. This only ever creates a new site; it never changes or replaces an existing one. The site is public on the internet immediately, so confirm with the user first.

publish_site

Read back the current source code of one of the user's existing GeminiLaunch sites, so it can be changed without rewriting it from scratch. ALWAYS call this before update_site when the user asks to change, edit, tweak, fix or add anything to a site that already exists — for example "change the heading on my bakery site" or "add a phone number to acme-cafe". update_site REPLACES the whole page, so editing without reading first destroys the rest of the design. Fetching the live URL is not a substitute: React sites render in the browser and return an empty page. Returns the source plus sourceKind, which says whether to send it back as react_code or html. Sites published from a ZIP or folder cannot be read back.

get_site

Set how one of the user's GeminiLaunch sites appears in Google and when its link is shared: the page title, meta description, social preview (OG) image and favicon — the same as "SEO & link previews" in the dashboard. Only the fields you pass are changed; pass an empty string to remove one. Images can be an https link or a base64 data: URL and are copied into GeminiLaunch storage. Replaced or removed images may be permanently deleted when no other site uses them. Before calling, confirm which site and existing fields or images the user wants to replace or remove. Works on every plan. Social apps may keep showing an old preview until their own cache refreshes.

set_seo_metadata

Take one of the user's custom domains off the site it is currently serving. The site stays published on its free GeminiLaunch address, and the domain stays on the account — still verified, ready to point at another site with attach_domain — so no DNS has to be redone. Use this when the user wants a domain freed up, or before pointing it somewhere else if they would rather do it in two steps. IMPORTANT: the first call is refused and tells you which site the domain is on. Report that to the user, ask whether to go ahead, and only call again with confirm_site once they have said yes. Detaching takes that site off its address immediately.

detach_domain