requests:write, requests:read and introductions:read, and introductions:write if it also confirms readiness.
1
Read the market, including capacity being auctioned
GET /radar/nodes with radar:read lists the market. Each node carries an auction field: null when nothing is being auctioned on it, and otherwise the lot that has not closed yet — its lot_id, format, ends_at, reserve_cents, bid_count and current_bid_cents.current_bid_cents is the leading bid, and only on an open lot that has drawn one. It is always null on a sealed lot before the close, for every reader including the lot’s own seller. Read it together with format and bid_count: an absent amount means “sealed” or “nobody has bid”, never “we did not send it”.Bidding is not available over the partner API, and a decided lot’s outcome is not either. Both are in the dashboard. See Bidding.2
Create a request when demand changes
POST /requests with requests:write. Send an Idempotency-Key on every write. See Idempotency. One of endsAt or durationMonths is required.request_invalid. problems lists every invalid field, so fix them together instead of retrying field by field.3
Keep it up to date while it is open
PATCH /requests/{id} replaces the specification. This works only while the request’s status is open. Once the GPU Outlet team offers it to a seller, status becomes matched and the request is frozen:4
Close it when demand goes away
POST /requests/{id}/close from either open or matched. Closing is final. A request cannot be deleted or reopened.5
Poll for introductions
Once a seller accepts a match in the dashboard, both companies are introduced. Poll with
introductions:read and side=buyer:GET /introductions/{id} reads a single one the same way. See Pagination for meta.nextCursor.The introduction carries the seller’s legalName and country, its reference (for example GO-20260917-K7M2QX), the frozen demand and listing, feeBasisPoints, and readiness timestamps. It does not carry the seller’s contacts. The seller reaches out to your company’s contacts.6
Confirm you are ready
POST /introductions/{id}/ready with introductions:write, once your company is ready to proceed. This needs a trader, an authorized signatory or an owner. A viewer’s key gets forbidden_role.Response
introduction_not_active.7
What continues in the dashboard
Once both sides are ready, the seller sends a deal invoice in the dashboard. Your company pays it directly to the seller, outside GPU Outlet. Deal invoices and receipts are available only in the dashboard. Sign in to see and act on them. See Buyer introductions.
Related
Seller workflow
What happens on the other side of the same introduction.
Idempotency
Safe retries for the writes in this workflow.
Errors
request_not_editable, request_invalid, introduction_not_active.Authentication
Scopes and company context this workflow relies on.