AI Assistant

AI Assistant is the account-level SHM workspace for explaining, diagnosing, and operating the current hosting account through the complete account-safe public API.

Where to find it: Open the account and choose AI Assistant. The menu appears only when AI is enabled for that account and the global provider configuration is ready.

Available to: The account user for their own account, plus root or the owning reseller while working in that account context.

What this page does

Use it for owned domains, DNS and DNSSEC, SSL, mail, files, PHP, Node.js, containers, Git, WordPress, databases, logs, resource usage, backups, and bounded diagnostics. It receives current endpoint parameters from the live AI catalog rather than guessing field names.

Before you start

Check the selected account and do not include passwords, API keys, private keys, or unrelated personal data in the prompt. A hidden or denied capability usually reflects role, ownership, feature policy, service state, or an intentional credential/session exclusion.

What it can do

• Read current account state and discover real resource identifiers.
• Run bounded account diagnostics and code search inside the account boundary.
• Explain every available parameter and accepted value before an action.
• Prepare or execute supported API operations under normal safety and confirmation rules.
• Verify a result through the corresponding read endpoint.

What it cannot do

• Reach another account or a root-only server route.
• Read or manage AI provider keys.
• Create an interactive terminal session or a WHMCS login ticket.
• Call private orchestration endpoints.
• Override a disabled feature, missing service, ownership gate, or required confirmation.

DNSSEC and external DNS

Account AI can discover DNS zone reads, record changes, DNSSEC state, enable, disable, and rollover operations, plus the documented Cloudflare surface. Registrar DS publication remains an external step and must be explained rather than silently assumed complete.

A safe request pattern

Ask: “Read the current state, show the endpoint and every parameter, explain the impact, and wait for confirmation before changing anything.” That sentence is not magic, but it gives the workflow a sensible spine.

How to use it

1. Open AI Assistant from the intended account.
2. Describe one concrete outcome and target.
3. Request current evidence and the complete endpoint contract.
4. Confirm a state-changing request only after reviewing its parameters.
5. Check the normal SHM page and external service after completion.

Result and next check

The assistant stays inside the selected account, uses a documented account-safe endpoint with complete parameters, and produces a result that can be verified independently.