GPU Price Data Permissions and Provenance

Price accuracy and publication rights answer different questions

An official API can help establish which price a provider reports. It does not automatically settle permission to collect, retain, display, export or resell its response. A comparison database also contains organization, normalization and annotations that should not be treated as permission-free merely because individual prices are factual.

The EU database directive distinguishes protections relating to databases and reuse of their contents. Which rules or contractual terms apply to a particular service requires its actual context and, where material, professional legal review. This article describes an engineering publication policy, not a jurisdiction-specific legal opinion or clearance for every provider.

Record the scope of each permission

For a new direct GPU source, the ByteCosts permission record has separate scopes for collection, caching, price display and machine-readable price export. It also records an evidence reference, reviewer, review date, next review deadline and any expiry. An unknown or expired grant leaves the source disabled.

The export scope includes browser-delivered data even without a public data API. A browser can receive structured prices in static JSON or JavaScript bundles. Hiding a download button does not make those data private. Conversely, raw source responses should not be committed to a public repository just because the production website hides them.

The current direct adapter’s registry starts pending. That is a deliberate limit: implementation and synthetic tests do not manufacture an authorization. The existing site’s older first-party records remain subject to their own source-specific review; the new gate is not a retroactive clearance of that catalog.

Discovery does not make an aggregator the source of record

An external directory can suggest which providers deserve research. It should not silently become a copied price feed or an alternative purchase route. Keep the observation source, underlying infrastructure provider and commercial purchase route distinct. A broker that can deploy an instance and an index that merely lists it play different roles.

ByteCosts’ accompanying historical inventory contains names and outbound source candidates, not a newly licensed bulk price dataset. A provider count does not establish current coverage. Some entries concern inference APIs, marketplaces, quotes or future capacity rather than a purchasable on-demand GPU instance.

An open-source collector’s software license also does not automatically license every external dataset it retrieves. GitHub’s licensing guidance explains why repository availability and licensing are separate. Review the actual data scope, notices and exceptions, not only a badge beside the code.

Respect access rules without confusing them with a license

The Robots Exclusion Protocol describes crawler directives and explicitly distinguishes them from access authorization. Respect applicable robots rules, terms, authentication boundaries and rate limits, but do not treat an allow directive as a redistribution grant.

Likewise, an API key establishes technical access under the relevant account arrangement; it is not a universal commercial data license. Do not evade authentication, challenge pages or blocks to maintain a price feed. A blocked source should fail visibly and retain its last reviewed observation without a new freshness timestamp.

Publish observations with their limitations intact

Every price should retain its acquisition source, observation time, purchase unit, currency, region and pricing option. An eight-GPU instance may have a useful derived per-GPU display price, but the minimum purchasable configuration must remain visible. A starting price, reservation, quote-only listing or unknown availability is not the same as a verified available on-demand offer.

The Azure Retail Prices documentation provides a technical basis for pagination, currency and meter interpretation. It does not resolve every downstream publication permission. ByteCosts therefore reviews those questions separately instead of relabeling a verified observation as licensed.

Source failures and unusually large price changes enter a local review flow. A human reviews the exact candidate hash before publication; builds perform no source fetching. See the source policy, the GPU explorer and GPU request economics for the distinction between a source observation and a calculation derived from it.