EQVPS API
Register, top up in crypto, and order a VPS entirely by code — no KYC, no human in the loop. Built for developers and for AI agents that provision their own servers.
https://api.eqvps.com/api/v1/eqvpsQuickstart
Four calls: from zero to a running VPS. Tokens below are placeholders — never paste a real token into a page.
# 1. Register — returns a Bearer token (no KYC, no human step)
curl -X POST https://api.eqvps.com/api/v1/eqvps/register \
-H "Content-Type: application/json" \
-d '{"first_name":"Ada","last_name":"Agent","email":"agent@example.com"}'
# → { "token": "<YOUR_API_TOKEN>" }# 2. Top up balance — pay in USDC / USDT / PYUSD, get a checkout URL
curl -X POST https://api.eqvps.com/api/v1/eqvps/balance/topup \
-H "Authorization: Bearer <YOUR_API_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"amount":20}'
# → { "checkout_url": "https://…" } # pay on-chain, balance credits automatically# 3. Order a VPS — paid from balance (get slug + os_id from GET /products)
curl -X POST https://api.eqvps.com/api/v1/eqvps/orders \
-H "Authorization: Bearer <YOUR_API_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"product":"micro","os_id":1,"ssh_key":"ssh-ed25519 AAAA…"}'# 4. Read SSH access — one-time root password is shown once here
curl https://api.eqvps.com/api/v1/eqvps/services/SV-XXXXXX \
-H "Authorization: Bearer <YOUR_API_TOKEN>"
# → { "status":"active", "ssh": { "host":"…", "port":22, "command":"ssh root@… -p 22" } }Key endpoints
The core surface. Open the interactive explorer for every parameter and response.
/registerCreate an account and get a Bearer token. No password, no human step./productsList all VPS plans with specs, price, and supported OS images./balance/topupCreate a crypto top-up invoice; returns a checkout URL. Balance credits on-chain confirmation./ordersOrder a VPS. Pays from balance if funded, otherwise returns an unpaid invoice./services/{id}Full status + live SSH access. The one-time root password appears here once./balancePrepaid credit balance and currency.See every endpoint, parameter and schema in the interactive explorer →
For AI agents
An agent can go from nothing to an operational server on its own — discover, pay, provision, and read SSH, all over the API or MCP.
MCP is live — not planned.
Point any MCP client at https://mcp.eqvps.com/mcp (Streamable HTTP). 26 tools cover discovery, account, payment and full VPS control. Public tools: list_plans, register_account, login; everything else takes a Bearer token.
Autonomous flow
1. register_account → get a Bearer token
2. topup_balance → pay the checkout URL in USDC/USDT
3. order_vps → provision from balance
4. get_vps_status → poll until active, read SSH (host, port, command, one-time password)Machine-readable resources
Errors
Standard HTTP status codes. Bodies carry a message field on failure.
200 / 201OK — request succeeded / resource created.401Missing or invalid Bearer token.403Authenticated, but not the owner of this resource.404Resource not found.409State conflict (e.g. an unpaid top-up already exists).422Validation error — check the request body.429Rate limited — back off and retry.Rate limits
Sensitive actions (order, top-up, password reset, reinstall, console) are rate-limited per account. Normal automation stays well within the limits; on a 429, back off and retry.
Ship against it now
Grab the spec, open the explorer, or read the full narrative reference with MCP setup.