Read domains, DNS, and hosting orders in Hostinger, then change things on approval
Connect Hostinger with an API key and your team can ask about the estate in plain language: which domains you hold, what DNS records resolve where, which WHOIS profile a domain uses, what a hosting order covers. Reads answer right away. Changes, like creating a WHOIS profile or a VPS public key, are previewed and sent for approval first.
24 tools: 20 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Hostinger run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create vps public key, create whois profile, delete public key, generate free subdomain. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Hostinger — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.