API & MCP Documentation
Rent and manage VPS programmatically — via REST API or MCP for AI agents.
How to pay
EQVPS accepts crypto directly — no card, no KYC. If you don't have crypto, you can buy it at checkout. Here's how each method works.
Pay with crypto directly (no KYC)
Place your order to reach the checkout page. You'll see the amount due and a deposit address with a QR code. From your wallet or exchange, send that amount of USDC or USDT on Base, Ethereum, Polygon, or Tron to the address. Once the network confirms the transfer, your server provisions automatically — usually within a couple of minutes. No sign-up with any third party, no identity check.
Connect a wallet
On the checkout choose "Connect wallet" and select yours — MetaMask, Phantom, Rainbow, Base Account, or any WalletConnect-compatible wallet. Approve the payment in the wallet popup and the order completes. No KYC.
Buy crypto first (KYC may apply)
No crypto yet? On the checkout, choose "Buy crypto" and pick a provider — PayPal, Binance, Coinbase, Cash App, Revolut and others. Pay with a card, Apple Pay, Google Pay, bank transfer, Skrill or Neteller; the provider sells you USDC and you send it to the deposit address to complete the order. If your local currency isn't listed, switch the currency to USD to see the full range of payment methods. These providers may require identity verification (KYC) on their side — that's separate from EQVPS, which never asks for KYC on direct crypto payments.
Networks & fees
We support USDC and USDT on Base, Ethereum, Polygon, and Tron. Base and Tron are typically the cheapest and fastest (Tron is widely used for low-fee USDT). The blockchain charges a small network fee (gas) on top of your payment. If you buy through an exchange, send slightly more than the exact amount so the full deposit arrives after the exchange's withdrawal fee.
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).
Quickstart — connect in one command
Step 1 — add the server (Claude Code, one command):
claude mcp add --transport http eqvps https://mcp.eqvps.com/mcpStep 2 — tell your agent, in plain language (copy-paste):
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.⚠️ The agent does everything via tools EXCEPT funding: a human sends crypto to the top-up invoice once. After the balance is funded, the agent orders VPS fully autonomously (pays from balance).
♻️ Repeat purchases with a funded balance are fully hands-off — just ask the agent.
🔧 Generic / OpenClaw / other MCP clients: use the JSON config block below.
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.
No crypto for your agent? A human can top up the account balance with crypto once — the agent then spends from that balance via the API without holding crypto itself.
MCP Tools
15 tools, grouped by purpose. Each maps to a REST endpoint.
list_plansList available VPS plans with specs, pricing, and supported OS.register_accountCreate an account, returns an API token.loginLog in, returns an API token.whoamiCurrent account info.get_balanceCurrent prepaid balance.topup_balanceTop up balance with crypto; returns a checkout URL.order_vpsOrder a VPS. Paid from balance if sufficient, else returns a crypto checkout URL.pay_invoiceGet a crypto checkout URL for an unpaid invoice.list_vpsList your VPS with status.get_vps_statusVPS details: status, specs, SSH access. Poll after ordering.power_vpsStart, stop, or reboot.set_hostnameChange hostname.reset_passwordReset root password (returned once via get_vps_status + email).reinstall_vpsReinstall OS — erases all data; vm stays.get_vps_metricsCPU, memory, network, disk over time.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}/metricsAuthenticated endpoints require Authorization: Bearer <token>.