API quickstart

This guide walks through a buyer stating demand and a seller reading their opportunities, with one key for each company. Create each key in Settings → API keys.

Confirm your key works

curl https://api.gpuoutlet.ai/v1/me \
  -H "Authorization: Bearer gpk_buyerkey..."

const res = await fetch('https://api.gpuoutlet.ai/v1/me', {
  headers: { Authorization: 'Bearer gpk_buyerkey...' },
});
console.log(await res.json());

Response

{
  "key_id": "3fa2c9e1-8b3e-4a1a-9c2a-4e2f6b1d9a70",
  "scopes": ["radar:read", "requests:read", "requests:write"],
  "mode": "live",
  "rate_limit_per_min": null
}

State demand

Create a request with requests:write. Every write to requests, opportunities and introductions needs an Idempotency-Key. Generate a fresh UUID per intent and reuse it exactly if you retry. Give either endsAt or durationMonths. One of the two is required.

curl -X POST https://api.gpuoutlet.ai/v1/requests \
  -H "Authorization: Bearer gpk_buyerkey..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 8f14e45f-ceea-467e-adc2-fb8c3f9f3e0a" \
  -d '{
    "gpuModel": "H100",
    "gpusPerNode": 8,
    "nodes": 4,
    "region": "us-east",
    "startsAt": "2026-10-01T00:00:00.000Z",
    "durationMonths": 6,
    "budgetMonthlyCents": 1200000,
    "currency": "USD",
    "notes": "Training run, flexible on exact start date"
  }'

const res = await fetch('https://api.gpuoutlet.ai/v1/requests', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer gpk_buyerkey...',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
    gpuModel: 'H100',
    gpusPerNode: 8,
    nodes: 4,
    region: 'us-east',
    startsAt: '2026-10-01T00:00:00.000Z',
    durationMonths: 6,
    budgetMonthlyCents: 1_200_000,
    currency: 'USD',
    notes: 'Training run, flexible on exact start date',
  }),
});
const request = await res.json();

Response (201)

{
  "id": "b6b6f6b0-6e0a-4e0a-9b0a-6f0a4e0a9b0a",
  "status": "open",
  "gpuModel": "H100",
  "gpusPerNode": 8,
  "nodes": 4,
  "region": "us-east",
  "startsAt": "2026-10-01T00:00:00.000Z",
  "endsAt": null,
  "durationMonths": 6,
  "budgetMonthlyCents": 1200000,
  "currency": "USD",
  "notes": "Training run, flexible on exact start date",
  "createdAt": "2026-09-17T14:02:11.000Z",
  "updatedAt": "2026-09-17T14:02:11.000Z",
  "closedAt": null
}

Read the request back

curl https://api.gpuoutlet.ai/v1/requests/b6b6f6b0-6e0a-4e0a-9b0a-6f0a4e0a9b0a \
  -H "Authorization: Bearer gpk_buyerkey..."

const res = await fetch(
  'https://api.gpuoutlet.ai/v1/requests/b6b6f6b0-6e0a-4e0a-9b0a-6f0a4e0a9b0a',
  { headers: { Authorization: 'Bearer gpk_buyerkey...' } },
);
const request = await res.json();

The response has the same shape as the create call. status moves to matched once the GPU Outlet team offers your request to a seller. From then on, the request cannot be edited. See Statuses and request_not_editable.

See the opportunity on a seller key

A key that belongs to a seller company reads its opportunities with opportunities:read. The buyer is not named. A seller sees only the anonymous demand until they accept and reveal in the dashboard.

curl https://api.gpuoutlet.ai/v1/opportunities \
  -H "Authorization: Bearer gpk_sellerkey..."

const res = await fetch('https://api.gpuoutlet.ai/v1/opportunities', {
  headers: { Authorization: 'Bearer gpk_sellerkey...' },
});
const { data, meta } = await res.json();

Response

{
  "data": [
    {
      "id": "7c1a2b3d-4e5f-6789-a0b1-c2d3e4f56789",
      "status": "offered",
      "listingId": "1a2b3c4d-5e6f-7890-ab12-cd34ef567890",
      "demand": {
        "gpuModel": "H100",
        "gpusPerNode": 8,
        "nodes": 4,
        "region": "us-east",
        "startsAt": "2026-10-01T00:00:00.000Z",
        "endsAt": null,
        "durationMonths": 6,
        "budgetMonthlyCents": 1200000,
        "currency": "USD"
      },
      "offeredAt": "2026-09-17T15:00:00.000Z",
      "decidedAt": null
    }
  ],
  "meta": { "nextCursor": null }
}

Accepting and revealing the buyer happens in the dashboard. The reveal commits the seller’s company to the success fee, so a person makes that call there. Over the API, a seller key can only decline. See the seller workflow.

Read introductions after a reveal

Once a seller accepts in the dashboard, both companies see the introduction. The buyer key reads it with side=buyer:

curl "https://api.gpuoutlet.ai/v1/introductions?side=buyer" \
  -H "Authorization: Bearer gpk_buyerkey..."

const res = await fetch('https://api.gpuoutlet.ai/v1/introductions?side=buyer', {
  headers: { Authorization: 'Bearer gpk_buyerkey...' },
});
const { data, meta } = await res.json();

Response

{
  "data": [
    {
      "id": "9d8c7b6a-5f4e-3d2c-1b0a-9f8e7d6c5b4a",
      "reference": "GO-20260917-K7M2QX",
      "status": "active",
      "side": "buyer",
      "listingId": "1a2b3c4d-5e6f-7890-ab12-cd34ef567890",
      "buyerRequestId": "b6b6f6b0-6e0a-4e0a-9b0a-6f0a4e0a9b0a",
      "buyer": { "legalName": "Acme Compute LLC", "country": "US" },
      "seller": { "legalName": "Northwind Silicon B.V.", "country": "NL" },
      "buyerContacts": [{ "email": "ops@acmecompute.example", "role": "owner" }],
      "capacity": {
        "demand": {
          "gpuModel": "H100",
          "gpusPerNode": 8,
          "nodes": 4,
          "region": "us-east",
          "startsAt": "2026-10-01T00:00:00.000Z",
          "endsAt": null,
          "durationMonths": 6,
          "budgetMonthlyCents": 1200000,
          "currency": "USD"
        },
        "listing": {
          "id": "1a2b3c4d-5e6f-7890-ab12-cd34ef567890",
          "title": "8x H100 SXM, us-east",
          "gpuModel": "H100",
          "region": "us-east"
        }
      },
      "feeBasisPoints": 100,
      "agreement": { "version": "1.0", "hash": "a1b2c3d4e5f6..." },
      "revealedAt": "2026-09-17T16:00:00.000Z",
      "tailEndsAt": "2028-09-17T16:00:00.000Z",
      "claimDeadlineAt": "2026-09-19T16:00:00.000Z",
      "closedAt": null,
      "readiness": { "sellerReadyAt": null, "buyerReadyAt": null }
    }
  ],
  "meta": { "nextCursor": null }
}

The buyer sees the seller’s legal name and country, not the seller’s contacts. The seller side of the same introduction sees the buyer’s legal name, country and contacts. For what each side does next, see the buyer and seller workflows.

Buyer workflow

Keep a request up to date, close it, confirm readiness.

Seller workflow

Poll opportunities, decline, confirm readiness.

Pagination

How meta.nextCursor works on list endpoints.

Errors

Every error code, including request_invalid and its problems.

Get started

Conventions

Workflows

Endpoints

Buyer workflow

Seller workflow

Pagination

Errors

​Related

Buyer workflow

Seller workflow

Pagination

Errors

Related