Verify a custom domain (step 2 of 2)
verify_custom_domainCheck the records from add_custom_domain (the ownership TXT and the routing record) and, when both are right, start serving the site on that domain; the HTTPS certificate follows automatically, usually within a minute or two. If it fails, the result names each record to add, change or remove; DNS changes can take a few minutes to propagate. Calling it again on a verified domain is a harmless re-check.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"siteName": "<siteName>",
"recordId": "<recordId>"
},
"name": "verify_custom_domain"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| recordId | Yes | The recordId returned by add_custom_domain. | |
| siteName | Yes | The site the domain was attached to. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | ||
| message | Yes | ||
| verified | Yes |