Discover machine-readable, seller-attributed GPU offers across configured registries. Let your CLI, API client, or participant-controlled policy evaluate candidates, then settle only the terms you choose.
CLI first · signed HTTP APIs · agent ready
Procurement is RFQ-like, not a central RFQ portal: sellers publish structured listings first, while buyer clients query selected registries and interact with storefronts through signed APIs.
Bring requirements to a market whose discovery, terms, policy, commitment, and delivery surfaces are machine-readable, inspectable, and programmable.
Query selected registries for machine-readable offers instead of treating one dashboard as the market.
Inspect resource, delivery, and settlement terms in a form your client and policy can evaluate.
Use participant-controlled policy or agents to compare and optionally negotiate across candidates, then explicitly agree or exit.
The buyer CLI drives payment settlement, storefront polling, and VM connection details or failure state.
A human-readable view of machine-readable listings before you automate procurement. Inspect the resource, provenance, settlement terms, and delivery constraints carried by each offer.
4× H200 · VM
New York · 96 vCPU · 768 GB RAM · 8 TB disk · NVSwitch
1× H100 · VM
Virginia · 24 vCPU · 192 GB RAM · 2 TB disk · PCIe
1× RTX 4090 · VM
California · 16 vCPU · 64 GB RAM · 1 TB disk · PCIe
Inspect the listed terms before you automate procurement
Open the market →The client carries machine-readable requirements from discovery and evaluation through optional negotiation, explicit agreement, payment settlement, storefront polling, and VM connection details.
market listing list --gpu-model H100 --gpu-count-min 1
market buy --gpu-model H100 --duration-hours 24Listed-price acceptance is the default; configured policy may accept, reject, propose, or time out. The buyer CLI supplies registry URLs, wallet and chain context, policy inputs, and an SSH public key before making signed storefront and settlement calls.
Read the buyer quickstart ↗Buyer and seller responsibilities stay visible instead of being collapsed into a platform promise.
Registries, requirements, aggregation, buyer policy, accepted chain/token choice, agreement or exit, SSH key, and settlement submission.
The offer, storefront policy, accepted settlement terms, infrastructure, provisioning, and delivery.