Do I need to write a custom AutoGPT block for EQVPS?

No. AutoGPT already ships an MCP block — 'Connect to any MCP server and execute its tools.' You give it our server URL (https://mcp.eqvps.com/mcp) and a Bearer token, pick a tool, pass arguments. That's the whole integration. A branded EQVPS block would only add a catalog icon; the MCP block already does the actual work.

How does the agent get a token?

It calls register_account — a public tool, no auth required. The response is a Bearer token immediately: no email confirmation, no OTP, no human step. You paste that token into the MCP block's credential field and every other tool call is authenticated.

What does the agent pay with?

A prepaid balance funded with USDC or USDT (Base, Ethereum or Polygon). order_vps debits the balance per order. The agent never holds your wallet keys and can't spend past the balance — that cap is your safety net.

Is it fully hands-off?

Ordering and management are. Funding isn't yet: a human (or a funded agent wallet) tops up the balance with crypto once, and after that the agent runs on its own. Per-request on-chain payment is on the roadmap, not shipped — we'd rather say that than pretend.

Which tools can the agent call?

The real ones: list_plans, register_account, order_vps, get_vps_status, pay_invoice, topup_balance, power_vps, set_hostname, reset_password, reinstall_vps, cancel_service. Note the names — it's order_vps, not create_server. If a guide tells you create_server or delete_server, it's guessing.

Give your AutoGPT agent its own server

A while back an AI agent signed up for EQVPS, put USDT on a balance, ordered a VPS, and read its own root credentials back — start to finish in about eighteen seconds, no human anywhere in the loop. It even handed us its own SSH public key at order time so it could log in without a password. Then, a day later, it came back and bought a bigger one.

That's the part people don't quite believe until they see it. An agent can write the code, debug it, and tell you where to deploy — but renting the actual box has always needed a person: a signup form, maybe an ID check, a card at a checkout page. The agent does the hard part and then waits on you for the boring part.

If you're building on AutoGPT, that gap is already closed. You just have to wire it up.

AutoGPT speaks MCP out of the box

Here's the useful bit most people miss: AutoGPT ships an MCP block. Its description is literally "Connect to any MCP server and execute its tools. Provide a server URL, select a tool, and pass arguments dynamically." You don't need a custom EQVPS integration — the generic block is the integration.

So the setup is short:

Add the MCP block to your agent graph.
Set server_url to https://mcp.eqvps.com/mcp.
Give it a Bearer token as the credential.
Pick a tool, pass arguments.

Step 3 is the only thing worth explaining, because it's where our design differs from a normal API.

Getting the token — no human, no email

Most hosts hand out API keys through a dashboard you log into. That doesn't work for an agent; the whole point is there's no person to click "generate key."

So register_account is a public tool. The agent calls it with a couple of fields and gets a Bearer token back in the same response — no email confirmation, no OTP, no verification screen. You take that token and drop it into the MCP block's credential field, and every subsequent call (order_vps, get_vps_status, and the rest) goes out authenticated. Under the hood the client just sends Authorization: Bearer <token> — nothing exotic, which is exactly why AutoGPT's MCP block talks to it without any special-casing.

If you'd rather not have the agent register itself, register once yourself, grab the token, and hand it over. Either works.

A real flow

Say you want the agent to spin up a box for a scraper. In tool calls that's:

list_plans → see the plans and, for each, the OS image IDs. Plan slugs are things like nano, micro, ai-agent-ip. OS is an os_id (a number from that list — Ubuntu 24.04, Debian 12, AlmaLinux 9), not a string like "ubuntu-24".
order_vps with { product: "nano", os_id: 1, ssh_key: "ssh-ed25519 AAAA..." }. Pass an SSH key and you get key-based root login straight away — strongly recommended for an agent, so it never has to handle a password.
get_vps_status → poll until it's active. This returns the host, port and a ready-to-paste ssh command. Root is usually reachable about a minute after the order; a fresh VM needs a moment to boot before SSH answers, so if the first attempt is refused, wait and retry — don't reinstall.

That's it. The agent now has a server it can SSH into and do whatever it was built to do.

Pay in crypto, skip the ID

Payment is a prepaid balance. You fund it with USDC or USDT — on Base, Ethereum or Polygon — and order_vps spends from that balance. No card, no billing address, no identity check. For an autonomous agent that matters twice over: there's no card form it can't fill in, and the balance is a hard ceiling on what it can spend. It literally cannot run up a bill past what you put on it.

There's also topup_balance and pay_invoice if you'd rather the agent drive funding through a checkout URL, but the simple model — fund once, let it order — is the one we'd reach for.

What's honest to say

Two things, because pretending otherwise would waste your time.

Funding isn't fully autonomous yet. Someone tops up the balance with crypto first; after that the agent is on its own for ordering and management. True per-request, pay-as-you-go on-chain billing is something we want, but it isn't wired up, and we're not going to claim it is.

The default plans are NAT, not a dedicated IP. On a NAT plan SSH comes in on a forwarded port (shown in get_vps_status) and maps to port 22 inside the VM — worth knowing if your agent sets up a firewall, because you allow port 22 inside, not the external port. If the agent needs its own public IPv4 (inbound services, its own web server), pick one of the -ip plans instead. For a worker that just makes outbound calls, NAT is fine and cheaper.

The takeaway

If you run agents on AutoGPT and you've been the human at the checkout, you can stop being that. Add the MCP block, point it at https://mcp.eqvps.com/mcp, let the agent register and order. Give it an SSH key and a funded balance and it'll have root on its own box in about a minute — and you'll only find out it happened when you check the logs.