Can an AI agent really run a hosting business, not just a single server?

Yes. The reseller side of EQVPS is exposed to MCP as 30 reseller_* tools, authenticated with a reseller token. An agent holding that token can operate the full client lifecycle — order a VM when a client pays, read its status, suspend on non-payment, unsuspend on settlement, renew and cancel — across a whole fleet of clients, not just one box. It is a business an agent can operate, not only a server it can rent.

What keeps an autonomous agent from spending out of control?

A prepaid balance. The agent pays for client VMs from a balance you top up in crypto, and it can never spend more than is on it. That is a hard cap independent of any prompt or bug: a runaway loop is bounded by the balance, not by your whole wallet. You set the operating policy; the balance sets the ceiling.

How is this different from an ordinary reseller program?

Ordinary reseller programs are operated by hand through a dashboard. Here the same reseller_* tools live on an MCP endpoint, so an AI agent can operate them directly — no human clicking through a panel for every order and suspension. Competitors offer manual reselling; the differentiator is that the whole operation is agent-operable through one MCP surface.

Is the reseller platform actually available?

Yes — the white-label reseller side is live, with the reseller_* tools reachable over both a REST API and MCP using a reseller token (rk_…). You can drive it from your own backend, from a dashboard, or from an agent, and mix all three.

Do you ask for ID or a card to run this?

No. You register with an email and fund a prepaid balance in USDC or USDT — no documents, no card, no KYC. That matters especially when it is an autonomous agent doing the provisioning and paying, with no human in the loop to present a card.

An AI agent that runs a white-label hosting business

A pattern no one else offers: an AI agent operates a white-label VPS reseller business end to end — ordering, provisioning, suspending and renewing client servers over 30 reseller tools on one MCP endpoint. Autonomous hosting, bounded by a prepaid crypto balance, no KYC.

Plenty of platforms let you use an AI agent. Almost none let an agent run the business. Because the reseller side of EQVPS is exposed to MCP, an AI agent can operate a white-label hosting operation end to end — ordering, provisioning, suspending and renewing client servers — with no human clicking through a panel. This is that pattern, described as a use-case.

What the agent actually operates

Authenticated with a reseller token (rk_…), an agent reaches 30 reseller_* tools over one MCP endpoint, covering the whole client lifecycle:

reseller_order_for_client — provision a VM under your brand when a client pays,
read its status and access,
reseller_suspend_client / reseller_unsuspend_client — pause on non-payment, restore on settlement,
renew and cancel as the client's billing dictates.

It is not operating one machine — it is operating a fleet on behalf of your clients. The same platform where an agent can buy and run its own server lets an agent run a hosting book.

Why this is a moat, not a feature

Every reseller program on the market is run by hand: a person logs into a dashboard for each order and each suspension. Exposing the reseller tools to MCP changes the category — the operation becomes agent-operable. You define the policy (when to provision, when to suspend, what to charge); the agent executes it continuously. Competitors sell manual reselling. The differentiator here is autonomy over the whole operation through a single MCP surface.

Bounded by design

Autonomy without limits is a liability, so the economics cap it:

Prepaid balance = hard ceiling. The agent pays for client VMs from a balance you fund in crypto and can never exceed it. A runaway loop is bounded by the balance, not your whole wallet.
Role-filtered token. rk_… reaches only the reseller_* tools — your clients and your plans, not the platform at large.
Your policy, its execution. The agent does what your rules say; it does not invent scope.

Who this is for

Builders of autonomous businesses who want a real, operable hosting business behind an agent, not a toy demo.
Existing resellers who want to remove the human from routine ordering and suspension entirely.
Crypto-native operators who want the whole thing funded and run without KYC or a card in the loop.

Honest scope

The token is a credential. It is the key to your client fleet; store and rotate it like one.
The agent executes policy, not judgment you did not give it. Bound its spend with the balance and its scope with the token.
You still own the customer relationship. Autonomy handles provisioning and lifecycle; support and billing decisions remain your brand's.

Start

The full tool reference — auth, the reseller_* tools, os_id, statuses — is in the reseller API / MCP docs. To wire an agent to the endpoint, see automating a reseller business over API and MCP and connecting an MCP client. The wholesale side is the white-label reseller program.