EverhostX

Clusters that self-heal.

World map of active workspaces

Evernode instances in use · country-level

Updated 2026-10-20T21:23:53.473Z — cached for ~120s.

When your main runner hits limits

When an AI agent exhausts its main‑runner’s context, time, or execution constraints, rent a temporary HotPocket workspace off to the side for bounded work — compiling, scraping, running tests, working a queue, or running untrusted code. You get a decentralized, WebSocket‑addressable HotPocket node with CPU/RAM/disk quotas — NOT SSH and NOT a full VM/Linux machine.

Treat it like a temporary HotPocket workspace. Spin one up to think in private, off the rest of your project, with nobody else on the box. Use it. If the job needs more hours, renew before the lease expires and keep going. When you are done, leave. The clock runs out and the instance is gone. Later you can spin up another for the next task.

Why an agent rents one

An agent can pay with x402 in XRP, get a 5-node HotPocket cluster on independent hosts in a few minutes (one order was fulfilled in 6m29s, with a 20/20 mesh and the app answering on all 5 nodes), deploy its app or contract, keep it alive by extending the leases, and run without a single host or cloud account it could lose. The Domain Credit Hub demo ran this way at https://dch.everhostx.com:36525.

What you get

Five HotPocket nodes on distinct networks (each a different ASN and IP prefix), spread across countries when the hosts allow it, linked into one HotPocket cluster with a full mesh (every node peered with the others).
The quote shows the planned host list before you pay. That list can still change while the cluster is acquired.
After payment, an authenticated fetch (claim token, or a proof signed by the paying account) returns each node's domain, user port, wss URL, and instance pubkey, plus the UNL and the upload keys. The keys are delivered on that first authenticated fetch. You can read them again until you confirm you saved them or the recovery window ends (20 minutes after the first delivery; a setting can only shorten that).
Security note: one upload key is shared by all 5 nodes in this cluster. If it leaks, every node is exposed, not just one. Store it like a master credential. Per-node keys are planned.

HTTP and DNS

Each node's handoff includes a WebSocket URL, wss:// on the host's domain and the user port assigned to that lease. That port is a TLS port.

EverhostX does not publish DNS for a buyer domain and does not issue a TLS certificate for one. To use your own name, point it at the node addresses with A records. The Domain Credit Hub demo does this: dch.everhostx.com has A records on two node IPs and is served on port 36525 (https://dch.everhostx.com:36525).

Pay with Xaman

What to buy

Optional sample preset (you deploy it; 1-node is not BFT)

Loading prices…

…

Xaman did not return a sign request. Paste the transaction hash after you send the payment.

Renew a temporary HotPocket workspace

Your previous orderId (preferred)

Or your leaseId

Hours to add

Renew anytime before the too-late buffer. If it is too late for the host extend to land, renewal is refused and your payment will not be accepted for this quote.

How an agent pays

Open the catalog to see what is on the shelf and the price.
Ask the shop for a quote at POST https://everhostx.com/quote with {"pay":"XRP"} or {"pay":"RLUSD"}.
Send that amount to the destination + destination tag. Wait for tesSUCCESS.
Claim with POST https://everhostx.com/buy and your transaction hash.
Still working? GET https://everhostx.com/renewals — when renewal is open, quote, pay, POST https://everhostx.com/renew before the clock hits zero.

Agents can pay for the cluster with x402:

POST /x402/cluster with the order JSON and no PAYMENT-SIGNATURE header. Pay defaults to XRP. Example body: {"nodes":5,"moments":3}. The route answers 404 unless X402_ENABLED=1.
An unpaid request returns HTTP 402. The body and the PAYMENT-REQUIRED header are the x402 v2 requirements. The XRP price on that requirement is in drops, with the destination, destination tag, and extra.invoiceId. The same 402 also lists RLUSD. When X402_BASE_ENABLED=1 and the Base mainnet check passes, it also lists USDC on Base.
Pay that XRP amount on the XRP Ledger to the destination and destination tag. Set InvoiceID to extra.invoiceId. On the transaction-hash path, also set memo everhostx:<quoteId>.
Retry the same POST with the PAYMENT-SIGNATURE header. For a payment already submitted, the header carries the transaction hash and a claim proof signed by the paying account (message everhostx-claim:<orderId>:<unixMs>). A signed transaction blob in that header is also accepted. HTTP 200 with status paid means the payment was accepted.

Agents: buy an awake desk → /llms.txt

For agents

Machine pitch: https://everhostx.com/why. Also /llms.txt and /pulse.