Skip to main content
The partner API lets your systems work with the GPU Outlet introduction marketplace directly, instead of through the dashboard. You can:
  • State demand and manage your requests for capacity.
  • Read the opportunities offered to your company, and decline the ones you cannot serve.
  • Read the introductions your company is party to, and confirm your side is ready.
  • Browse Radar, ask about a Radar listing, and submit nodes for review by the GPU Outlet team.
  • See which Radar nodes are being auctioned, and on what terms.
Base URL:
Every request and response body is JSON, except the spec itself. The API has no session cookie and no CORS. You call it with an API key, not from a browser tab signed in to the dashboard.

The contract

The full contract is an OpenAPI 3.1 document. It is served without authentication, so you can read it before you have a key:
The Endpoints section of this documentation is generated from that same document.

What stays in the dashboard

Some steps carry legal or financial weight and are done by a person in the dashboard:
  • Accept an opportunity and reveal the other company. The reveal commits your company to the success fee, so it is a decision a person makes in the dashboard. A key can decline, never accept.
  • File an existing relationship claim. A claim carries a statement and an evidence file that the GPU Outlet team reviews.
  • Deal invoices, receipts and success fee invoices. These carry documents and lead to payments.
  • Sign agreements. Signing happens in a dialog on our signing page, has legal effect, and asks for your second factor.
  • Accept a lot’s terms, bid, and open or amend a lot. The API reports that a Radar node is being auctioned; everything you do about it is in the dashboard. A decided lot’s outcome is not read over the API either. See Bidding.
A key can do only what the scopes table lists. Company details, team members, verification, listings on My Listings, API keys and notification settings are managed in the dashboard.

Authentication

Create a key, understand scopes and company context.

API quickstart

State demand and read it back, end to end.

Buyer workflow

Integrate a buyer’s planning system.

Seller workflow

Integrate a seller’s inventory system.