Skip to content
HOSTACKER

Developers

One API for every layer of your stack

Compute, managed applications, AI endpoints and GPU jobs share one authentication model, one resource shape and one set of guarantees.

Read the docsExplore MCP
~/projects/northbound-apizsh
$npm i -g @hostacker/cli$hostacker login✓Authenticated as alex@northbound.dev$hostacker servers listNAME              STATUS    PLAN      REGIONproduction-api    running   cloud-4   us-eastpostgres-prod     running   cloud-8   ca-eaststaging-api       stopped   cloud-2   eu-central

Surfaces

Three ways in, one control plane

Whichever surface you use, the same policies, budgets and audit logging apply.

  • CLI

    Install once, authenticate once. Inspect and change infrastructure from the same shell you already work in.

  • REST API

    Predictable resources, cursor pagination and idempotency keys on every mutation. Errors are typed, not free text.

  • MCP server

    The same operations exposed as agent tools, with spending limits and approvals enforced server side.

API

Hostacker Core API

A small, stable surface area. Below is the planned shape of the v1 resources.

localhost:3001/v1REST
  • GET/v1/servers
  • POST/v1/servers
  • GET/v1/servers/{id}
  • POST/v1/servers/{id}/restart
  • GET/v1/apps/templates
  • POST/v1/ai/endpoints
  • GET/v1/usage
  • GET/v1/invoices

  • Estimate before mutate

    Any call that creates or resizes a resource can be run in estimate mode first and returns the exact monthly delta.

  • One resource shape

    Servers, apps, endpoints and GPU jobs share the same envelope: id, status, region, cost and timestamps.

  • No provider leakage

    The API never returns provider identifiers. Your integration depends on Hostacker, not on whoever is underneath.

The Hostacker Core API is not live yet. This page documents the intended v1 contract so integrations can be designed against it. Phase 2

Example

Create a server in one request

Idempotent, estimable, and explicit about cost before anything is provisioned.

request.shcurl
curl -X POST https://api.hostacker.com/v1/servers \
  -H "Authorization: Bearer $HOSTACKER_API_KEY" \
  -H "Idempotency-Key: 8f2c1a90" \
  -d '{
    "name": "production-api",
    "region": "us-east",
    "plan": "cloud-4",
    "image": "ubuntu-24-04",
    "ssh_keys": ["key_laptop"]
  }'
response.json201 Created
{
  "id": "srv_a1f4c9",
  "name": "production-api",
  "status": "provisioning",
  "region": "us-east",
  "plan": "cloud-4",
  "ipv4": "51.123.45.67",
  "resources": {
    "vcpu": 2,
    "memory_gb": 4,
    "storage_gb": 80
  },
  "monthly_cost": 11.99,
  "created_at": "2026-08-27T18:00:00Z"
}

Build against a stable contract

Design your integration now and connect it the day the Core API ships.

Get startedRead the docs