Hostinger, In Full, Inside 0n3: 363 Endpoints and a One-Call Site Launch
Hostinger's whole developer API is now inside 0n3, generated from their own docs, with a one-call site launch built on top: domain in, live WordPress site out.
Bottom Line Up Front (BLUF) **Every Hostinger API endpoint is now a callable inside 0n3 — 363 of them across 12 product areas — and the first thing built on top is a single call that takes a bare domain and puts it live on your Hostinger plan: site created, domain linked, DNS written, plugins deployed.** Connect Hostinger once with one API token in your 0nVault, and every 0n product, agent and automation can reach it.
What shipped
| Piece | What it is |
|---|---|
Catalog service hostinger | 363 endpoints: VPS (63), web hosting (51), Reach email marketing (49), domains (39), mail (38), WordPress (38), agency hosting (36), ecommerce (29), billing (9), DNS (8), Horizons (2), domain verification (1) |
| Generated, not typed | A script walks Hostinger's own API reference and reads the method, path and description off every endpoint page. When Hostinger adds endpoints, one run regenerates the whole service. |
Mini-app hostinger_site_launch | Domain in → live site out. Portfolio check, optional purchase, agency or hosting order, WordPress setup polled to completion, domain link, A and www records when the zone is at Hostinger, plugin deploys. |
| One token | A Hostinger API token from hPanel, pasted once on 0n3.app/connect. Never a password, never copied into another app. |
Why this matters
Hosting has always been the part of "launch a client site" that needed a human in a control panel. Create the site, wait, link the domain, edit DNS, install WordPress, install the plugins, then go tell the SEO tool the site exists. With Hostinger's API inside 0n3 that whole chain is one receipt-producing call, and every step lands in the receipt with Hostinger's own answer. Nothing is reported as live until Hostinger says it is.
That is the foundation for the offer we are building toward: one agency plan, every client site created under it by API, and CRO9 wired in on the same run so the site is scored, watched and improved from day one.
What we measured before writing a line
- Hostinger's API sells domains (899 TLDs), VPS and email. It does not sell hosting plans. A plan is bought once in hPanel; after that the API creates as many sites under it as the plan allows. The launch app knows this: on an account with no plan it stops and says so, having made only read calls.
- The API host is
developers.hostinger.com. The singular host that appears in prose does not resolve. Small thing, one hour of confusion avoided for the next person. - Their doc pages embed neighbouring endpoints, so a naive scrape mislabels about one in ten paths. The generator now picks the operation that matches each page's own name.
How to connect it
- In hPanel go to Account → API and create a token.
- On 0n3.app/connect, add it as a key under the service name hostinger.
- Ask any 0n3-connected agent to list your websites, or run the site launch with a domain.
What is next
- CRO9 on the same run. The launch app will provision the new site in CRO9 so scanning and daily briefs start the moment the site exists.
- 0nTask project links. A project locks to a GitHub repo, a Vercel project, and now a Hostinger site, so the AI can read and write the actual site behind the task.
- VPS. The same catalog already covers virtual machines end to end: create, snapshot, firewall, malware scan. The one-call launch for a VPS-hosted stack is the natural follow-up.
FAQ
Does 0n3 store my Hostinger password? No. It stores the API token you create, encrypted in your 0nVault, and mints nothing else.
Can it buy a domain? Yes, through Hostinger's billing API, but only when you explicitly pass buy_domain: true and a payment method. It never spends money on a default.
Which plan do I need? Any Hostinger web hosting plan works for single sites. For creating client sites by API, the Agency plan is the one built for it.