---
title: "Price ladder for one instance type: spot, on-demand, 1-year and 3-year commitments, with discounts."
method: GET
path: "/v1/term/instance"
tags: ["term"]
---

# Price ladder for one instance type: spot, on-demand, 1-year and 3-year commitments, with discounts.

`GET /v1/term/instance`

## Request

- Base URL: `https://cloud.trycorpus.ai`
- URL: `https://cloud.trycorpus.ai/v1/term/instance`
- Auth: one of:
  - API key in header `PAYMENT-SIGNATURE`
  - API key in header `Authorization`
  - API key in header `X-Api-Key`

Current prices from our series: spot median across zones (where spot events exist), on-demand list price, and reserved/reservation terms as effective hourly with upfront amortized. `discount_pct` is relative to on-demand. AWS carries four reserved terms (1y/3y × no/all upfront), Azure two (1y/3y all upfront), GCP two resource-based committed-use terms (`cud_1y`, `cud_3y`, no upfront).

## Query parameters

- `provider` 'aws' | 'gcp' | 'azure', required
- `region` string, required
- `instance` string, required

## Response `200`

Ladder.

- TermLadder
  - `provider` string
  - `region` string
  - `instance` string
  - `unit` string
  - `note` string
  - `terms` TermPoint[]
    - `term` 'spot' | 'ondemand' | 'ri_1y_no_upfront_standard' | 'ri_1y_all_upfront_standard' | 'ri_3y_no_upfront_standard' | 'ri_3y_all_upfront_standard' | 'cud_1y' | 'cud_3y', required
    - `label` string
    - `price` number, required: USD per hour for the instance.
    - `since` string
    - `discount_pct` number: Percent below on-demand.
    - `zones` integer: spot only: zones behind the median.

## Other responses

- `400`: Invalid or missing parameter.
- `402`: Payment required. The x402 v2 payment requirements are in the PAYMENT-REQUIRED header (base64 JSON) and repeated as the JSON body: `accepts[]` lists every offer (USDC on 13 networks: eip155:8453, eip155:143, eip155:1, eip155:43114, eip155:42161, eip155:10, eip155:137, eip155:130, eip155:146, eip155:480, eip155:1329, eip155:999, eip155:5042) with amount and payTo address. Circle Gateway offers cover every listed network; a Coinbase-facilitated offer covers Base. The same response carries an MPP challenge (WWW-Authenticate: Payment, USDC on Tempo). Retry with a PAYMENT-SIGNATURE header or an MPP credential, or let an x402 or MPP client (for example `circle services pay` or `mppx`) handle it; a prepaid key in X-Api-Key is charged instead of a 402.
- `404`: Unknown provider, region or instance type.
- `503`: The store is still warming up after a restart; retry in a minute. No payment is taken.

---

[API](https://skmtc.dev/trycorpus/apis/corpusai-cloud-pricing-api.md) · [All operations](https://skmtc.dev/trycorpus/apis/corpusai-cloud-pricing-api/llms.txt) · [OpenAPI document](https://skmtc.dev/trycorpus/apis/corpusai-cloud-pricing-api/revisions/cb0754f4d151?raw)