How do I automate provisioning as a reseller?

You get a reseller token (rk_…) in the Partners cabinet and call the same MCP endpoint (or the REST API) with it. The token is role-filtered: it exposes 30 reseller_* tools covering the full client lifecycle — create a plan, add a client, order a VM for them, read status, suspend, unsuspend, renew, cancel. Ordering a server for a client becomes one authenticated call instead of a dashboard session.

What is the difference between the API and MCP here?

Same capabilities, two front doors. The REST API is what you script from your own backend or billing system. The MCP endpoint exposes those same reseller_* tools to an AI agent or an MCP-capable client, so a model can operate them directly. You can use either or both — a billing webhook that provisions over REST, and an agent that handles the rest over MCP.

Can an AI agent actually run the ordering and suspension?

Yes — that is what the MCP surface is for. Because the reseller tools are exposed to MCP, an agent authenticated with your rk_ token can order a VM when a client pays, read its status, suspend it on non-payment and unsuspend on settlement, all without a human clicking through a panel. You set the policy; the agent executes it.

How is my reseller access authenticated and scoped?

With a reseller token (rk_…) sent as Authorization: Bearer rk_… . It is role-filtered to the reseller_* tools only, so it operates your clients and your plans, not the platform at large. Keep the token secret like any credential; it is the key to your whole client fleet.

Do I have to automate everything at once?

No. Start by provisioning from the dashboard, then move the highest-volume actions to the API as you grow — usually order-on-payment and suspend-on-non-payment first. The point is that operational effort stops scaling with client count once those two are automated, which is what makes a large reseller book profitable.

Automating your VPS reseller business over API and MCP

A reseller business that runs by hand hits a ceiling fast: every order, every suspension, every renewal is a human clicking through a panel, and your time scales with your client count. The way past that ceiling is to run the operation as code — and EQVPS exposes the reseller side over both a REST API and an MCP endpoint, so you can script it or hand it to an AI agent.

One token, 30 reseller tools

You get a reseller token (rk_…) in the Partners cabinet and send it as Authorization: Bearer rk_…. That token is role-filtered: it exposes 30 reseller_* tools over the same MCP endpoint, covering the full client lifecycle:

create a plan and set its price,
add a client,
reseller_order_for_client — order a VM under your brand,
read its status,
reseller_suspend_client / reseller_unsuspend_client — pause and restore,
renew and cancel.

Ordering a server stops being a dashboard session and becomes one authenticated call.

API or MCP — same capabilities, two front doors

They are not competing options; they are two ways into the same tools:

REST API — what you script from your own backend or billing system. A payment webhook fires, your code calls the order endpoint, the VM is provisioned under your brand.
MCP endpoint — the same reseller_* tools exposed to an AI agent or MCP-capable client, so a model can operate them directly.

Most resellers use both: a billing webhook that provisions over REST, and an agent that handles the messier judgment calls over MCP.

The moat: an agent that runs the operation

This is where it stops looking like every other reseller program. Because the reseller tools are on MCP, an AI agent authenticated with your rk_ token can operate the business directly — order a VM when a client pays, read status, suspend on non-payment, unsuspend on settlement — without a human in the loop. The same platform where an agent can buy and run its own server lets an agent run a fleet on behalf of your clients. You set the policy; the agent executes it. That is the AI-run hosting business as a concrete pattern.

A minimal flow

// authenticate every call with your reseller token
// Authorization: Bearer rk_...

reseller_order_for_client({ client_id, product: "small", os_id: 1 })  // provision under your brand
// → service_id, ip, access — deliver it to your client as your own
reseller_suspend_client({ service_id })       // on non-payment
reseller_unsuspend_client({ service_id })      // on settlement

Four calls stand in for what used to be a dashboard session per client, per event.

Honest scope

The token is a credential. rk_… is the key to your whole client fleet — store it like one, and rotate it if exposed.
Automation executes your policy, not its own. An agent ordering and suspending is only as good as the rules you give it; keep spend bounded by your prepaid balance so a bug or a bad prompt cannot run away.
You still own support and billing. Automation removes the clicking, not the customer relationship.

Where to go next

The full reference — auth, the reseller_* tools, os_id handling and statuses — is in the reseller API / MCP docs. New to the business side? Start with how to start a VPS reseller business. The wholesale side is the white-label reseller program.