Other GPU rental marketplaces

Other GPU rental marketplaces

Vast.ai is one of many marketplaces where an independent host lists hardware and renters run their own containers. Each admits hosts by its own rules — bare metal or a VM, Kubernetes, a static address, identity checks, staking, minimum hardware — and pays in money or in its own token. The capability catalog's market family declares every seller, so stado capabilities market lists them with their support: vast, stado (peer lending) and handtohuman are implemented; RunPod Community Cloud, SaladCloud, Clore.ai, Akash, io.net, Chutes and Darkbloom are declared planned, with no Stado adapter yet. Every marketplace Stado carries is one adapter behind the same interface: list, unlist, status, earnings, maintenance, measure, serve-or-rent, readiness, monitor and follow are each answered by the adapter --provider names, with the marketplace's own operation or a refusal saying why that marketplace has none (a peer fleet states no earnings and publishes no prices), and the same adapter answers its rows in stado capabilities market. A new marketplace is a catalog row, a provider id and one adapter, so the commands, the capabilities report and Desktop reach it with no other change; its readiness check names the rule that refuses a host, so a host is offered wherever it is admitted and earns most. Every stado market command's --provider reads the same family: a name the family does not declare is refused listing the sellers it does, and a planned seller is refused with its catalog note, saying Stado carries no adapter for it yet. --peer is refused with any provider but stado, and --resource with any but handtohuman.

stado capabilities market (and Desktop's capabilities operation with family market) also asks, on the host it runs on, whether each seller can sell from there now: Vast's readiness verdict, each declared peer fleet's readiness, and for a planned seller its support and note. A seller that is not ready is printed not ready with its own sentence and does not stop the others being read; with --json the rows are sellers[] of {provider, peer?, ready, verdict}. The bare stado capabilities makes no such network read. The sellers are read in the order stado capabilities select market --order vast,stado,… writes to capabilities.market.order, then every seller it does not name in the catalog's order; select refuses a seller the family does not declare or one named twice, and an order in the configuration that names an undeclared seller is printed as an order row with that cause while the catalog's order stands.

HandToHuman

stado market list --provider handtohuman --resource gpu|egress --price-gpu USD --units N
stado market status --provider handtohuman --resource gpu|egress
stado market earnings --provider handtohuman --resource gpu|egress --target HOST
stado market unlist --provider handtohuman --resource gpu|egress
stado market readiness --provider handtohuman

A host offers its compute (per GPU-hour, HandToHuman's compute kind) or its residential egress (per gigabyte, residential-egress) on HandToHuman through HandToHuman's own handtohuman market CLI on its PATH; Stado never touches HandToHuman's database. The seller is the account the host declares as market.handtohuman.seller (STADO_HANDTOHUMAN_SELLER), one HandToHuman created with a worker role. list creates the offer at --price-gpu USD per unit (sent in cents) for --units units, with metadata naming the host as pinned_host so a compute order's dispatch runs back on this host, and keeps the offer id in the fleet store at market/handtohuman/<host>/<resource>.json; unlist withdraws that offer and forgets it, status shows it, and earnings reads handtohuman market order list --offer and sums the totals of the accepted orders (an accepted order's escrow is released to the seller less HandToHuman's platform fee) per currency; --json prints stado.handtohuman-earnings.v1 with every order. Refusals: --resource cpu or disk (HandToHuman sells no such kind), a missing --resource or --units, Vast.ai's --price-disk or --price-min-bid, a price not above zero, no declared seller, an offer already listed for the resource, unlist, status or earnings with none listed, the handtohuman program missing or refusing (its own sentence quoted), and maintenance, measure, serve-or-rent and follow, which HandToHuman has no counterpart for. readiness answers ready once a seller is declared and HandToHuman's offer list answers. Desktop's Registry screen lists, withdraws and reads earnings.