Search real-time domain availability and prices (via Name.com).
Pass a keyword for suggestions, or include ONE full domain name anywhere
in the query ("orivox.ai", "www.orivox.ai", even inside a short phrase)
to also get that exact domain availability-checked and returned as the
FIRST result marked exact:true. Response markers: exact_domain = the
exact answer is in the list; exact_check_unavailable = the exact check
failed, the list is keyword suggestions only (relay the included note);
NEITHER marker = no single domain was recognized (bare keyword, or two+
domains in one query) and NO exact check ran -- if the user asked about
specific domains, use check_domain per domain. Returns suggestions as
{domain, available, price, premium, renewal_price} sorted
purchasable-first (exact match first when present), plus registrar_env
("production" or "sandbox").
ALWAYS mention two pricing traps when recommending: premium=true is an
aftermarket domain (first-year price can be thousands, renewal differs),
and renewal_price much higher than price is a first-year-discount cliff
(e.g. $3.99 year one, $48.99/year after) -- quote both numbers. If the
response carries sandbox=true, relay the included caveat to the user in
their language and do not present results as real availability. This is a
READ: searching never reserves, registers, or charges anything.
STOP after presenting the results. Do NOT call get_domain_purchase_link in
the same turn: that tool is the PAYMENT step, and the user is still
choosing. Report the names, prices and renewal cliffs, then wait. Only once
the user picks ONE domain and says they want to buy it does the purchase
link belong in the conversation -- a payment link handed to someone who has
not decided is clutter at best and pressure at worst. Searching more, or
checking another name with check_domain, needs no link at all.