Participants
Company
The party that buys or sells on GPU Outlet. Every request, listing, agreement and introduction belongs to a company, not to a person. A person belongs to one company. See Company.Buyer
A company that needs reserved GPU capacity. A buyer browses Radar, sends requests and pays GPU Outlet nothing.Seller
A company that offers GPU capacity. A seller is verified, signs the seller agreement, publishes listings, accepts opportunities and pays the success fee. One company can be both a buyer and a seller.Role
What a person may do for their company. There are four roles:- Owner: everything, including inviting members and changing roles. A company always keeps at least one owner.
- Authorized signatory: signs agreements, applies for verification, publishes listings, and works on requests and introductions.
- Trader: works on requests, opportunities and introductions, but does not sign, verify or publish.
- Viewer: can look at the market but cannot act for the company.
Authorized signatory
A member who may sign agreements for the company. Owners may sign too. The signing page is prepared in the name of the owner or authorized signatory who joined the company first.The GPU Outlet team
The people who review verification, prepare matches, decide existing relationship claims and handle success fee invoices.Before the introduction
Verification
The check GPU Outlet runs on a seller company before it can publish listings. The seller applies as a Direct provider or an Authorized reseller. See Verification.Seller agreement / Buyer agreement
The two marketplace documents listed on Documents: the Seller marketplace agreement and the Buyer marketplace agreement. A seller must have signed the current version of the seller agreement to accept an opportunity. A buyer can send requests before signing the buyer agreement. See Agreements.Listing
Capacity a seller publishes from My Listings: the GPUs, the price, the availability and the proof of the right to sell it. See Listings.Radar
The screen where buyers browse published listings. Sellers appear under a handle such asSeller-XXXXX, not their legal name. See Radar.
Listing status
The badge on a Radar listing: Verified Direct, Verified Allocation or Indicative. It reflects the seller’s verification kind and proof of the right to sell. See Statuses.Request
What a buyer needs, stated once: GPU, GPUs per node, nodes, region, start, term, and an optional monthly budget. Sellers see the demand without the buyer’s name or notes. See Requests.Sale type
How a listing is sold, answered when it is published and fixed there: Reserve at a fixed price, or Sell by auction. See Selling by auction.Lot
Capacity put up for competitive bidding, with its own terms and a closing time. A lot is built from a listing and may take some or all of its nodes. See Bidding.Bid
A buyer’s stated intention to buy a lot at a price, and their place in the ranking. It is not a payment, it reserves nothing, and no money moves when it is placed. A company has one live bid per lot; bidding again replaces it.Open and sealed
The two lot formats. On an open lot the current best bid is visible to anyone. On a sealed lot no bid is visible to anyone until the lot closes, the seller included. The format is fixed when the lot is created.Reserve
Two things, depending on the screen. On a lot, the seller’s published floor: a bid at or above it clears, and a lot with none takes any bid. On a Radar card, the Reserve button, which sends an inquiry about the listing and sets nothing aside. See Reserve and confirmation requests.Bid step
The increment a lot’s bids are quoted in. On an open lot it is the smallest raise over the current best bid; on a sealed lot it is the granularity, counted from the reserve.Terms version
The version of a lot’s own terms, shown asN.0. A bidder accepts a specific version, and every amendment raises it and voids earlier acceptances.
Clearing price
The winning bid’s amount on a decided lot. It is shown to everyone who can see the result; the ranking and the losing amounts are shown to nobody.Match
The link the GPU Outlet team makes between a buyer’s request and a seller’s listing. A match reaches the seller as an opportunity.Opportunity
A match as the seller sees it: the anonymous demand, with no buyer name, country or notes. The seller accepts and reveals, or declines. See Opportunities.Accept and reveal
The seller’s decision to accept an opportunity. It shows both companies to each other and starts an introduction under the success fee terms. It is done in the dashboard, not over the partner API.The introduction
Introduction
The record that starts when a seller accepts a match, or when a lot closes with a winner. It freezes the demand, the listing, the fee terms and the agreement version at that moment. While active, its status is Protected. The success fee applies to contracts signed within 24 months of the reveal. See Buyer introductions and Seller introductions.Reference
A readable identifier for a record. Quote it when you contact support.Existing relationship claim
A seller’s statement, with evidence, that it already knew the buyer. It must be filed within 2 business days of the reveal. If the GPU Outlet team approves it, no success fee is owed on that buyer.Business day
Monday to Friday in UTC. Public holidays count as business days.Ready
Each side’s confirmation that the companies have spoken and agreed to go ahead. It is a fact, not a contract, and cannot be undone. The seller can send an invoice once both sides are ready.Deal invoice
The seller’s own invoice to the buyer, uploaded as a PDF on the introduction. The buyer pays it directly and marks it as paid. The seller confirms when the money arrives.Fees
Success fee
What a seller pays GPU Outlet: 1% of every amount actually received from an introduced buyer. It applies to contracts signed within 24 months of the reveal. Buyers pay no fee. See Success fee.Success fee invoice
The invoice GPU Outlet issues each time a seller confirms money received on a deal invoice. It is due 5 business days after the seller confirms Money received and is paid by bank transfer.API
Partner API
The HTTP API athttps://api.gpuoutlet.ai/v1 for working with Radar, requests, opportunities and introductions from your own systems. Radar inquiries and node submissions are available only in the partner API. Accepting and revealing, claims, invoices, signing and bidding stay in the dashboard. See Partner API.
API key
A secret that authenticates partner API calls, sent asAuthorization: Bearer gpk_…. Keys belong to a user and act for that user’s company and role. You create keys in Settings → API keys. See Authentication.
Scope
A permission attached to an API key, such asrequests:read or introductions:write. A call succeeds only if the key has the scope the endpoint needs.
Related
How it works
See the terms in the order they happen.
Statuses
Every status label and what it means.