Specification · Class 3 · indicator — a constructed measure that is not a price
GAP-H100 · Grid Assessed Price — H100 spot
The daily provider-pooled median of availability-verified, executable H100 SXM-class 80GB on-demand asks — one vote per provider. GAP-H100 names the spot leg of the term structure; it is not an exchange print and not a cleared price. Posted list prices are a secondary check, never an input (methodology v3, effective 2026-07-24).
series id gap_h100_spot · methodology v3.0 · unit usd_per_gpu_hr
Ⅰ · Class and status
Part B class · print status · latest print of recordClass 3 · indicatorPrinting
Class — and why
Reclassified assessment → indicator by methodology change notice 2026-08-14 §2 (panel of two nominal contributors, one static for its entire history; 50.3% of realised variance is panel composition). Printing continues unbroken. Path back to assessment class: at least two independently moving contributors, plus the minimum-observation rule.
Latest print of record · read from storage, not recomputed
| Series id | Registry label | Methodology | Latest print | Value | Note |
|---|
| gap_h100_spot | GAP-H100 (spot) | v3.0 | 2026-09-07 | $3.2000/GPU-hr | |
Ⅱ · Specification
A4 field template · honest current state · n/a fields shown, not hidden| Code | GAP-H100 (spot)series id gap_h100_spot · stable, never reused |
| Accelerator class | NVIDIA H100 SXM-class, 80GBgpu_model prefix "H100 SXM"; PCIe and NVL variants are excluded from this code |
| Interconnect / topology | Not normalisedSXM-class offers of any node size enter; multi-GPU machine offers are reduced to a per-GPU price at ingest and tracked as distinct configuration series. Node/cluster topology is not a normalisation axis today. |
| Contract basis | On-demand, executable asksspot / interruptible and reserved tiers are excluded from this code (they are separate series or not assessed) |
| Term | Hourly, no commitment |
| Commitment | Nonethe listed hourly ask for one bookable machine; no minimum quantity or spend basis |
| Region | Not normalisedasks enter as listed by the venue, from any region; regional normalisation is in development |
| Inclusions | The listed hourly compute ask onlystorage, egress, support tier and orchestration are outside the price and are not normalised |
| Currency / unit | US$ per GPU-hour, printed to four decimals |
| Assessment close | 18:30 UTC — the scheduled daily cycle anchorThe print date is the cycle date, derived from the scheduled anchor and never from wall-clock time (incident of record 2026-08-06). Observations are those captured in that cycle's collection run. |
| Submission cut-off | None — no submission channel is open. Participation v0 (submission definition, mailbox, receipt discipline) is at /standards/participate; no submission has been received. |
| Publication time | With the daily print (masthead: 04:30 AEST) — on the briefing, /instruments, the daily report, /api/print/<date> (permanent) and MCP. |
| Data hierarchy applied | Tier 2 — bids and offers (tier-2 bookable asks, availability-verified). Tier 1 concluded transactions: 0. Judgment: none (arithmetic).Disclosed on every print in the provenance stamp (notice 2026-08-14 §3): panel size, each contributor's unchanged-days, transactions, data tier, judgment. |
Ⅲ · Contributing panel (v3 + admission registry, notice 2026-08-20)
inputs of record| Leg | Source | Disposition & filter |
|---|
| Vast.ai | marketplace API (keyed) | MEMBER — rentable=true · rented=false · verified=true · reliability ≥ 0.95 |
| RunPod | GraphQL API | BENCHED from 2026-08-28 by scheduled registry event (founder ruling 2026-08-20 — rescheduled from 2026-08-21 to the earliest replacement-leg qualification date so panel depth never decreases) — static posted list (unchanged for its entire stored life, first row 2026-05-10); MEMBER until then with unchanged-days disclosed on every stamp; from the scheduled date collection continues, rows disclosed on the stamp, never in the level or the min-obs count |
| Lambda (on-demand) | public pricing page | QUALIFYING from 2026-08-21 — 7 consecutive clean collection days before first inclusion; no availability signal exposed |
| Hyperstack | public pricing page | QUALIFYING from 2026-08-21 — 7 consecutive clean collection days before first inclusion |
Admission is a dated registry event (velocity GAP_PANEL, both runtimes): bookable/executable asks only; auto-bench at ≥ 14 consecutive unchanged days; reliability-floored where the source exposes one. Not in the panel, stated plainly: SF Compute operates the market's only orderbook clearing-price feed; its terms of service bar republication of derived market data without written consent, so it is not ingested (citable with attribution, as OCPI/Ornn is). Thunder Compute was refused panel wiring 2026-08-20 on the same class of terms (systematic-retrieval and commercial-republication bars; T&C read of record on file).
Ⅳ · Normalisation and construction rules
the named adjustments, in order- Class filter — gpu_model prefix "H100 SXM" only.
- Tier filter — on-demand only; spot / interruptible / reserved rows never enter this code.
- Sanity bounds — offers outside US$0.20–30.00 per GPU-hour are excluded (spec-table garbage guard).
- Per-GPU price — multi-GPU machine offers are divided to a per-GPU rate at ingest and tracked as distinct (provider, SKU) configuration series.
- One vote per provider — each provider's offers are reduced to a median first; the level is the median across providers, so a marketplace listing many machines cannot outweigh a provider quoting one price.
- Level and change are separate — the level describes today's panel; the published change is the median of like-for-like changes across matched (provider, SKU) pairs present at both endpoints. A basket-composition change never produces a printed move. Fewer than three matched pairs: no change is published (velocity, one shared module per runtime).
- Freshness is measured by price change, not row presence — a contributor whose price is unchanged for ≥ 7 consecutive days is classified static and carried in the provenance stamp with its unchanged-days.
- Panel admission & benching (effective 2026-08-21) — a leg must be a bookable/executable ask, pass 7 consecutive clean collection days before first inclusion, and is benched automatically at ≥ 14 consecutive unchanged days (2× the static threshold; the executable leg's historical maximum run is 3 days). An explicit future-dated bench in the registry (a scheduled bench) is itself a dated registry event and supersedes auto-bench until it binds — the leg remains a member with its unchanged-days disclosed on every stamp. Benched and qualifying legs keep being collected and are disclosed with their disposition and reason; their rows never set the level and never count toward the minimum-observation rule.
Ⅴ · Minimum observations and withholding
below which the print is flagged · below which it is not publishedRule adopted 2026-08-16 (unmodified from the 2026-08-14 proposal), binding from the 2026-08-22 print: the daily print is WITHHELD — disclosed with the provenance stamp, never a silent gap — when fewer than two providers contribute on the day, or every contributor is unchanged for ≥ 7 consecutive days. Until it binds, prints continue with the provenance stamp and indicator class disclosing the condition. Below the withhold line the print is flagged, not fabricated.
Ⅵ · Disclosures
verbatim from the derived-series registry · the same string every surface carriesGAP-H100 (spot) — Reclassified 2026-08-14 from assessment to indicator: the panel holds two nominal contributors, one static across its entire 93-day history, and 50.3% of the printed series' realised variance is panel composition, not price. Printing continues unbroken. Returns to assessment class when the panel carries at least two independently moving contributors (methodology change notice 2026-08-14). Minimum-observation rule adopted 2026-08-16, binding from the 2026-08-22 print: the daily print is withheld — disclosed as WITHHELD with the provenance stamp, never a silent gap — when the panel has fewer than two contributing providers or every contributor is unchanged for 7 or more days (methodology change notice 2026-08-16).
Ⅶ · Revision history
dated changelog for this code · never rewritten| Date | Version | Change | Reference |
|---|
| 2026-05 | v1 | All-variant H100 median, mixed tiers. | — |
| 2026-06-12 | v2 | SXM-class only; on-demand tier filter; provider-pooled median; SKU normalisation at ingest. | — |
| 2026-07-24 | v3 | Executable-ask panel (availability-verified); posted lists demoted to secondary check; reserved 1-yr leg added; GTS-1Y term-structure print introduced. Announced as 2026-07-25; effective date corrected 2026-07-27 — the v3 panel governed the 2026-07-24 print one cycle before its announced date (publish-before-effect breach, correction of record 2026-07-27). | docs/corrections/2026-07-25-gap-v3-effective-date.md |
| 2026-08-14 | — | Reclassified assessment → indicator (Part B Class 3); printing unbroken; path back stated. Provenance stamp added to every print (no notice period — disclosure only). | docs/methodology-notices/2026-08-14-instrument-actions.md §2, §3 |
| 2026-08-14 | — | Minimum-observation rule proposed under its own notice. | docs/methodology-notices/2026-08-14-gap-minimum-observation-proposal.md |
| 2026-08-16 | — | Minimum-observation rule adopted unmodified; notice period 2026-08-17 → 2026-08-21; binds from the 2026-08-22 print. Withheld days are a sibling record carrying the full provenance stamp. | docs/methodology-notices/2026-08-16-gap-minimum-observation-decision.md |
| 2026-08-20 | — | Panel admission & benching rule adopted (effective 2026-08-21): bookable/executable asks only; 7-day qualification window; auto-bench at ≥ 14 unchanged days (a scheduled — explicit future-dated — registry bench supersedes auto-bench until it binds); reliability floor where exposed. RunPod bench SCHEDULED for 2026-08-28 by founder ruling 2026-08-20 (static for its entire stored life, first row 2026-05-10; rescheduled from 2026-08-21 to the earliest replacement-leg qualification date so panel depth never decreases, unchanged-days disclosed on every stamp meanwhile); Lambda on-demand and Hyperstack registered QUALIFYING. Levels and like-for-like changes read panel members only from the effective date; history stands. | docs/methodology-notices/2026-08-20-panel-admission-and-benching.md |
Ⅷ · Downstream, surfaces, notices, sources
where it flows · where it shows · what governs itDownstream series
- Grid Basis (OCPI − GAP-H100 spot) — the GAP leg.
- GCCX divergence — the physical composite's GAP leg (chain-linked across declared breaks, v1.1).
- RWI self-host (GAP-spot) columns for RW-S and RW-L.
Surfaces
- / (index strip + term-structure module, provenance stamp)
- /instruments §Ⅰ
- /providers
- /api/print
- /api/mcp get_term_structure
Notices that govern this code
Sources of record
scripts/compute_gap_print.pyscripts/velocity.py ↔ dashboard/lib/velocity.tsscripts/derived_series.py ↔ dashboard/lib/derived-series.tsdocs/gap-methodology-v3.mddocs/gap-methodology-v3.md (print discipline, decision of record 2026-07-24)
This page renders the method of record for GAP-H100; it does not define it. Printed values are never rewritten — a change in method is announced by notice before it affects a print (publish-before-effect); a correction restates only what the day’s own information set supported. Permanent print URLs: /api/print/<date>.