Call domain.transfer_out
Give the member the steps to move a domain we bought them to another registrar — 'I want to move my domain elsewhere', 'how do I transfer this out?', 'get me the auth code'. Give the customer the exact steps to move a domain we registered for them to another registrar, and say whether it may leave yet. We can't do the move for them — the unlock and the authorization code are done in the registrar's own dashboard — so relay guided_step in order. Relay the eligibility reason WORD FOR WORD: eligible means no hold is visible from the registration date, NOT a guarantee the transfer will be accepted. This prepares only; nothing is transferred by this call. Not for pointing it at another site here — that is domain.point_at_site. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/domain.transfer_out
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 4 revisions of this API.