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, location, markup })
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).