Reseller API & MCP (white-label)

Typical flow

Create a plan, add a client, order a VM for them; deliver the access from your own brand.

// Reseller token (rk_...) from the Partners cabinet -> Authorization: Bearer rk_...
// One MCP endpoint, role-filtered: a reseller token exposes the 30 reseller_* tools.
reseller_create_plan({ name, cores, ram_gb, disk_gb, ipv4, ipv6, locations, markup_price })   // ipv4 0-4, ipv6 0-1, at least one
reseller_add_client({ email }) -> { client_id }
reseller_order_for_client({ plan_id, client_id, os_id? })   // os_id: see list_plans catalog
reseller_vm_details({ service_id }) -> { access, password }  // deliver to your client

os_id is optional — omit for the location's default OS. For a specific OS, use an os_id from the public list_plans catalog; it resolves to the right image per location.

Operating systems & os_id

14 Linux images are available (below). Pass os_id in reseller_order_for_client — take it from the public list_plans catalog. Note: available_os may list different ids per location; the os_id from list_plans resolves to the correct image for the plan's location. Omit os_id to use the location's default OS.

VM statuses

active — running. provisioning — being created (brief async window right after ordering). suspended — paused (e.g. you suspended the client, or non-payment); reactivate with reseller_unsuspend_client. cancelled — terminated (VM removed).

Connect any agent or tool

One MCP endpoint — mcp.eqvps.com/mcp — authenticated with your reseller token. Plug it into whatever you already use.

# Claude Code - add the reseller MCP server (token: Partners cabinet -> API)
claude mcp add --transport http eqvps-reseller https://mcp.eqvps.com/mcp \
  --header "Authorization: Bearer rk_YOUR_RESELLER_TOKEN"

// Claude Desktop / Cursor / Windsurf - mcp.json
{
  "mcpServers": {
    "eqvps-reseller": {
      "type": "http",
      "url": "https://mcp.eqvps.com/mcp",
      "headers": { "Authorization": "Bearer rk_YOUR_RESELLER_TOKEN" }
    }
  }
}

# LangChain / LangGraph (Python) - langchain-mcp-adapters
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient({"eqvps": {"transport": "streamable_http",
  "url": "https://mcp.eqvps.com/mcp",
  "headers": {"Authorization": "Bearer rk_YOUR_RESELLER_TOKEN"}}})
tools = await client.get_tools()   # 30 reseller_* tools

# Raw MCP (JSON-RPC) - n8n HTTP, Zapier/Make, cURL, any language
curl -X POST https://mcp.eqvps.com/mcp \
  -H "Authorization: Bearer rk_YOUR_RESELLER_TOKEN" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{
        "name":"reseller_order_for_client","arguments":{"client_id":123,"plan_id":45}}}'
# List tools first: {"jsonrpc":"2.0","id":1,"method":"tools/list"}

Ready-to-use agent prompts

Auto-renew

Client servers renew without manual work. reseller_set_autorenew toggles it per VM (ON by default); a daily job renews anything expiring within 3 days from your wholesale balance. Renew now for N periods with reseller_renew (months 1-24). On a short balance you get one alert and the normal grace window — never a silent loss.

Sandbox testing (dry-run)

Pass test: true to reseller_order_for_client (or POST /api/reseller/orders with {"test":true}) for a dry-run: you get a mock response whose structure is identical to a real order, but no VM is created and no balance is charged. Use it to verify your API/MCP integration end-to-end before going live.

Client email notifications

By default EQVPS emails the account on provision/suspend/terminate/password/reinstall. In the reseller cabinet you can turn “Notify clients by email” off to handle client notifications yourself (white-label) — provisioning and renewals still work, just silently.