API & MCP Documentation

How to pay

You don't need to already own crypto — a card works too. EQVPS takes crypto directly (just an email, no KYC), and right at checkout you can buy the crypto with a card, Apple Pay or Google Pay. Here's how each method works.

Account & billing

Everything after the first order — promo codes, renewing, upgrading.

MCP for AI Agents

EQVPS exposes a Model Context Protocol (MCP) server so AI agents can discover plans, order a VPS, pay from a prepaid balance, and manage servers — autonomously. The endpoint speaks Streamable HTTP (the 2026 remote-MCP standard).

claude mcp add --transport http eqvps https://mcp.eqvps.com/mcp

Register an EQVPS account, show me plans, create a crypto top-up invoice for $20, then once I confirm payment, order 2 Ubuntu 24.04 VPS and give me their SSH access.

Connect your agent

Add this to your MCP client config (Claude Desktop, or any remote-HTTP MCP client):

{
  "mcpServers": {
    "eqvps": {
      "type": "streamable-http",
      "url": "https://mcp.eqvps.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Get a token by calling register_account or login through the MCP server itself. The list_plans tool works without a token (discovery).

Authentication

EQVPS uses Bearer tokens — but there are two SEPARATE auth paths, do not mix them. AI agents: call register_account (or login) through this API/MCP — the agent supplies its own credentials and gets a token instantly, with NO email and NO OTP code. Send it as Authorization: Bearer <token>. Humans on eqvps.com sign in with a passwordless email OTP code — that browser flow is for people only and an agent cannot use it (it cannot read email). An agent must use register_account, never the email-OTP flow. list_plans needs no token.

MCP Tools

15 tools, grouped by purpose. Each maps to a REST endpoint.

Example flow

A typical agent session: discover, register, fund, order, manage.

// 1. Discover plans (no auth)
list_plans()
// 2. Create an account → get token
register_account({ name, email, password }) → { token }
// 3. (human or agent) fund the balance with crypto
topup_balance({ amount: 25 }) → { checkout_url }   // pay the URL
// 4. Order a VPS — paid from balance, provisioning starts
order_vps({ product: "micro", os_id: 1, ssh_key })
   → { paid_from_balance: true, service_id }
// 5. Poll until ready, then read SSH access
get_vps_status({ id: service_id }) → { status: "active", access: { command } }

REST API

Every MCP tool is backed by a REST endpoint you can call directly. Base URL: https://api.eqvps.com

GET  /api/v1/eqvps/products
POST /api/v1/eqvps/auth/register
POST /api/v1/eqvps/auth/login
GET  /api/v1/eqvps/balance
POST /api/v1/eqvps/balance/topup
POST /api/v1/eqvps/orders
POST /api/v1/eqvps/invoices/{id}/pay
GET  /api/v1/eqvps/services
GET  /api/v1/eqvps/services/{id}
POST /api/v1/eqvps/services/{id}/power
POST /api/v1/eqvps/services/{id}/hostname
POST /api/v1/eqvps/services/{id}/reset-password
POST /api/v1/eqvps/services/{id}/reinstall
GET  /api/v1/eqvps/services/{id}/metrics

Authenticated endpoints require Authorization: Bearer <token>.