Glossary¶
Seller — An account that offers GPU capacity. Seller fees are seller-paid (see Paying).
Buyer — An account that searches for capacity, agrees a deal, and runs jobs on it.
Listing — A seller's offer of capacity: a capability (GPU model, count, memory, network, region, availability, price) plus a title. New listings are drafts; they go live only after the machine is measured and the listing is revalidated.
Whole GPU — A full physical device allocated to one buyer (device_class: whole, isolation whole_device).
Slice — Part of a GPU offered on its own. Today only NVIDIA MIG slices with a known profile are admitted. AMD partitions that share a driver interface are not supported, and overlapping device ranges are refused.
Machine / node — A computer running the seller agent and paired to one listing.
Pairing code — A short-lived code (XXXX-XXXX) created for a listing; the agent uses it once to register the machine.
Heartbeat — A signed message the agent sends every minute. Metering credits the time between two heartbeats for each allocated device.
Edge verifier — A standalone service that challenges the machine with a capacity proof and signs a one-use verdict that the API checks.
Proof — A challenged capacity proof: a compute check (matrix product checked with Freivalds' algorithm) and a commit-then-open memory check. See Proofs.
Verified — A badge meaning the GPU itself was proven to hold the claimed capacity. It is currently off for every machine (fail-closed). See Verified badge.
Deal — A match between a buyer and a listing. It is non-binding until both sides accept terms and any required human approval clears.
Tranche — An hourly slice of delivery used for metering, fees, holdback and payout.
Agent key — An API key with the omk_ prefix, issued to an agent on your account.