check_domain_availability

com.atom/premium-domains · Verify this server

Check whether ONE specific, fully-spelled domain is available, taken, or a premium listing. Use whenever a user names a specific domain (e.g. "is acme.com available?", "who owns x.io?", "can I get nova.ai?"). For open-ended "suggest names for my idea" requests use search_brandable_domains instead. If the user wants to PURCHASE a domain they already know is an Atom marketplace listing, use get_domain_details or get_domain_purchase_pay_link instead — this tool checks fresh-registration availability, which will misleadingly report an already-listed/owned domain as "taken." Returns: status ("available" = registrable now | "taken" = registered/unavailable | "premium" = for sale on Atom), registrable (bool), price + currency when applicable, estimated_value (rough appraisal, optional), and alternatives[] — when the domain is taken or premium, the closest available premium names from Atom (each with domain, price, url) so the user always has a buyable path. Also returns a top-level url (an Atom /name/ page). IMPORTANT — the top-level url is only meaningful when status is "taken" or "premium": that page exists to view/buy an existing Atom marketplace listing. When status is "available" (a fresh, unregistered domain), there is nothing to show on that page — do NOT mention or show this url to the user at all in that case. Just state that the domain is available and registrable, with nothing else. Separately, and regardless of the url: when status is "available" and the user wants it, do NOT tell them to register it on the website themselves. Continue the purchase yourself, in this same conversation, via register_domain (the user's Atom balance) or register_domain_spt (Stripe card) — both quote a real price and confirm with the user before charging anything. If either reports error registrant_contact_required, that's expected and not a dead end: ask the user for their name, phone, address, city, and country, call create_registrant_contact with those, then retry the registration call — do not send them to the dashboard link unless they explicitly prefer to enter it there themselves.