Fixing x402 REST usage
corpusAI Cloud Pricing: One day's fixing for a ticker: median USD per GPU-hour of eligible quotes, with low, high and count.
cloud.trycorpus.ai · 18 listed services · provider site
corpusAI Cloud Pricing: One day's fixing for a ticker: median USD per GPU-hour of eligible quotes, with low, high and count.
corpusAI Cloud Pricing: Reserved / reservation price history of one instance type (AWS standard RIs 1y/3y no-upfront/all-upfront; Azure reservations 1y/3y).
corpusAI Cloud Pricing: Capacity stress score, 0 (slack) to 100 (tight), for one GPU model on one day, with every component.
corpusAI Cloud Pricing: Price ladder for one instance type: spot, on-demand, 1-year and 3-year commitments, with discounts.
corpusAI Cloud Pricing: On-demand list-price history of one instance type.
corpusAI Cloud Pricing: Price currently in force per zone and product for one instance type.
corpusAI Cloud Pricing: Full monthly history for one instance type, back to 2014 for legacy AWS types.
corpusAI Cloud Pricing: Hourly time-weighted OHLC bars for one instance type.
corpusAI Cloud Pricing: Full daily history for one instance type, all eras stitched.
corpusAI Cloud Pricing: Latest rental quotes for one GPU model across neo-clouds, marketplaces and other clouds.
corpusAI Cloud Pricing: Current spot price of every type and zone in every region of a provider, in one call.
corpusAI Cloud Pricing: Azure spot eviction-rate history (28-day buckets, sampled daily).
corpusAI Cloud Pricing: Every ticker's fixing for one day in one call.
corpusAI Cloud Pricing: Current reserved effective hourly price of every instance type and ri_type in a region (AWS or Azure).
corpusAI Cloud Pricing: Daily USD per GPU-hour index per provider and market for one GPU model, with hyperscaler spot legs.
corpusAI Cloud Pricing: Raw spot price-change events for one instance type.
corpusAI Cloud Pricing: Daily capacity stress scores for one GPU model.
corpusAI Cloud Pricing: Term structure per hyperscaler for one GPU model, USD per GPU-hour: spot, on-demand, 1y, 3y.
Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.