Can AI agents automate Hostinger?

Hostinger is automatable today through its public API. This record is Hostinger hosting, domains, DNS, email, VPS, WordPress, ecommerce, and billing as exposed by that API. It is not the separate n8n product named on the Hostinger site. The API is mostly REST over HTTPS. The base URL is https://developers.hostinger.com and paths look like /api/hosting/v1/websites. Send an API token from hPanel as Authorization: Bearer. Responses are JSON. The documented limit is 90 requests per minute per user, with 429 and Retry-After when it is exceeded. Some endpoints, including domain availability, are metered separately. A 202 response means the call was accepted and finishes asynchronously. The same overview says the CLI, SDKs, and MCP server are generated from the OpenAPI specification. Official SDKs are named for PHP, Python, and TypeScript. The CLI example is brew install hostinger/tap/hostinger and then hostinger hosting websites list, with browser sign-in. The MCP overview says @hostinger/mcp exposes 372 tools, or the hosted server at https://mcp.hostinger.com can be used with browser OAuth. The hostinger/api-mcp-server README, opened the same day, says the unified binary hostinger-api-mcp covers 415 operations and that a local token in HOSTINGER_API_TOKEN skips OAuth. Those two counts differ. A separate Mail API is named for mailbox send and read and is not fully mapped here. https://docs.hostinger.com/llms.txt is a documentation index. iPaaS catalog pages were not opened. Computer-use viability is unassessed. The API and MCP both score 8. The API is the best path because a bearer token calls the OpenAPI without an MCP client. The CLI scores 6 because the opened page shows install and one list command, not the full command set.

Best path today: api · Overall automatability: 8/10