Published 07:13 AEST · Before US Open · Wednesday, 9 September 2026Pipeline 04:30 AESTVol. I  No. 121
The Grid
Independent Price Reporting for the Compute Market
thegridco.ai
EST. 2026 · SYDNEY
The Priced Unit · what a buyer actually signs

A headline $/GPU-hour is not what a buyer signs.

The priced unit in a negotiated compute deal is a specific commitment: an accelerator and memory configuration × a quantity × a term × a region × a delivery schedule × an SLA × a prepay structure × the terms negotiated alongside price. Two quotes with the same headline rate can be materially different deals — the headline-rate-versus-effective-cost point is made once, here: everything below is about the dimensions that carry that difference.

The commitment's dimensions

ruling of record 2026-08-24

The ruling of record (2026-08-24) binds the check to this dimension set: the parsed deal renders as the structured commitment record, correctable before the read runs, and the read compares per dimension— your value · the observed range or bucket where tier-disclosed data exists · “not held” where it doesn’t. What each dimension means commercially, and what the check reads today:

DimensionWhat it prices, commerciallyWhat the check reads today
Accelerator + memory configurationWhich chip, which memory class and size, which form factor — an H100 SXM 80GB and an H100 PCIe are different priced units.Read: the accelerator against a fixed model registry (off-registry names are stated, never guessed) and the interconnect where stated. Memory configuration is read only incidentally inside model strings — its promotion to a first-class field is ruled (2026-08-24) and lands with a versioned parse change.
QuantityGPU count and node shape. Price per unit moves with scale; so does the delivery question.Read: the quoted count, bounds-checked.
TermCommitment length and start date — the difference between spot exposure and a multi-year obligation.Read: term in months, bounds-checked. Register comparison buckets term as spot / 6mo / 12mo / 24mo with no cross-term inference, ever.
RegionWhere the capacity physically sits — power cost, latency, data-residency and the available supply all differ by region.Read: the stated region. Register comparison narrows to region only when BOTH sides state one and they normalise equal — disclosed either way.
Delivery scheduleWhen the capacity actually arrives — immediate, staged ramp, or a dated future window. A cheap price for capacity that arrives late prices a different thing.Read: today it lands in the co-negotiated-terms bucket; its promotion to a first-class field is ruled (2026-08-24) and lands with a versioned parse change.
SLAUptime commitment, service credits, remedies — what happens when the capacity fails.Read: the stated SLA phrase.
PrepayPayment schedule and prepaid fraction — a 25% prepay changes the effective cost of the same headline rate.Read: the stated prepay/payment-schedule phrase.
Co-negotiated termsEverything else the deal settles: power passthrough, egress, termination rights, upgrade clauses, quantity flexibility, support tier.Read: up to ten further material terms, kept verbatim as the residual bucket and scanned against the customary-terms checklist below.

What is customarily negotiated alongside price

the registry the check's checklist runs on

The check reads every paste against this registry — the assessment-specification field template — and marks each item present ●, absent ○, or excluded ⊘ (the quote expressly refuses it or carves it out of the price — disclosed, never credited as settled) in the reply. A quote that settles only price and quantity has left most of the commitment’s value terms unwritten:

01Price and unit
02Quantity and configuration (count, node size)
03Term length and start date
04Interconnect and topology (SXM/NVLink · fabric)
05Delivery / availability window
06SLA, uptime and service credits
07Power & cooling — passthrough or included
08Egress / networking charges
09Prepay and payment schedule
10Termination rights and liquidated damages
11Upgrade / generation-transition clause
12Quantity flexibility (burst / downscale)
13Support tier and escalation

How the comparison works today

check-architecture, v1 limits stated

Every comparison is deterministic arithmetic over dated stored records — one model call reads your text, and no model ever writes a market figure. The published v1 rules:

  • Accelerator class is matched exactly via the model registry — no cross-model inference, ever.
  • Term is bucketed (spot / 6mo / 12mo / 24mo) from the offer’s own stated term — no cross-term inference.
  • Region narrows the comparison only when both your quote and the register row state one and they normalise equal — disclosed either way.
  • Two offers make a range; one offer is one offer, never presented as a range; every figure carries its evidence tier (bookable asks / posted list — tiers 4–5) and its own date.
  • The assessed position is H100-only today — the only assessed instrument is the H100 spot leg; other classes get the register read, and the reply says so.
  • No unit conversion is attempted. A $/GPU-month or total-price quote is displayed but not converted for positioning — a conversion would smuggle assumptions (hours per month, utilisation) into a figure.
  • No percentile below 5 comparable observations (the create-floor published at /standards/participate); aggregates render WITHHELD below 2 observations and nothing is cited from a cohort smaller than 5.

What “not held” means

honest at n=0, by construction

Where The Grid holds no tier-disclosed observations for a dimension, the read says “not held” — no bucket is invented, no figure is imputed, and nothing is papered over to make the reply look fuller. That is the same minimum-observation discipline the daily print runs under: a day below the floor renders WITHHELD, never a carried-forward number.

“Not held” is also the invitation: a confirmed submission is the thing that opens a class — the first dated observation of its kind in the record, sealed into the chained ledger. The comparison you get is built from the contributions of buyers before you; the check is where both halves of that bargain happen.

THE GRID PUBLISHES CONDITIONS AND INPUTS — MARKET OBSERVATION, NEVER INVESTMENT OR PROCUREMENT ADVICE.sources: the customary-terms registry · check-architecture · ruling of 2026-08-24