List locations
Lists the locations you can create instances in, and what each
offers: TEEs, public IP modes, IPv6 and private networks. Every
create names its location; defaultFor is the location a client
offers first for a TEE.
AuthorizationBearer <cc_...>An API key of your org, sent as Authorization: Bearer cc_.... Keys
start with cc_ and are otherwise opaque. Treat a key as a password:
anyone holding it can act with its scopes until it expires or is
revoked. Each operation's security requirement lists the scopes it
needs; an empty list means any valid key. The MCP server at /mcp
accepts agent keys and no other kind.
pageSize?integerThe most items to return.
1 <= value <= 10050pageToken?stringThe nextPageToken of the previous page, unchanged. Send the same
filters with it.
1 <= length <= 2048Api-Version*stringThe API version the request is written against. This document
describes 2026-10-15. A missing header returns
400 api_version_required, and a version the API does not serve
returns 400 unsupported_api_version.
X-Correlation-ID?stringAn id of your own for this request, or for a group of requests, to
find them in our logs and yours. Logged with the request and returned
unchanged in X-Correlation-ID. The request id itself is always the
API's own, in X-Request-ID.
^[A-Za-z0-9._:-]+$1 <= length <= 128Org-Context?stringAdmin keys only: the id of the org to act in. Required with an admin
key, together with Access-Reason; with any other credential it
returns 400 invalid_request. Every request that carries it is
recorded in that org's operator-access log.
^org-[a-z0-9]([-a-z0-9]*[a-z0-9])?$5 <= length <= 63Access-Reason?stringAdmin keys only: why the operator is acting in the org, such as a
support ticket. Required with Org-Context. Recorded, verbatim, in
the org's operator-access log.
^[^\x00-\x1F\x7F]+$10 <= length <= 500A page of locations.
application/json- response
items*array<>nextPageToken?NextPageTokenPass it back as pageToken for the next page. Absent on the last page.
curl -X GET 'https://api.cloud.confidential.ai/v1/locations?pageSize=50&pageToken=eyJjIjoiMjAyNi0xMC0yMlQxNzowMjoxMVoiLCJpIjoiaS03azJtOXE0eDFiZmEifQ' \ -H 'Api-Version: 2026-10-15' \ -H 'X-Correlation-ID: rollout-2026-10-22' \ -H 'Access-Reason: Support ticket 4821: customer asked why i-6d3f9h2k8mzr failed'{ "items": [ { "id": "us-west-1", "displayName": "US West (Hillsboro, Oregon)", "country": "US", "tees": [ "tdx", "sev-snp" ], "publicIpModes": [ "shared", "dedicated" ], "ipv6": false, "privateNetworks": false, "defaultFor": [ "tdx", "sev-snp" ], "services": [ { "name": "instances" }, { "name": "clusters" } ] }, { "id": "ca-east-1", "displayName": "Canada East (Beauharnois, Quebec)", "country": "CA", "tees": [ "sev-snp" ], "publicIpModes": [ "shared", "dedicated" ], "ipv6": false, "privateNetworks": false, "defaultFor": [], "services": [ { "name": "instances" } ] } ]}List sizes GET
Lists every instance size, CPU and GPU, with its vCPUs, memory, the TEEs it is offered on and its hourly price: what your org pays, with any deal on its subscription, or the list price before it has one. Sizes are a fixed catalog of shapes: a create names one by `id` and takes no vCPU, memory or GPU count of its own. An id is a family, a dot and a count. The family is a letter for what it is for and a digit for the hardware generation: `c1` (compute) has 2 GiB of memory per vCPU, `s1` (standard) 4 GiB and `m1` (memory) 8 GiB, and a GPU family adds its GPU model, as in `g1-b300`. The count is of vCPUs, or of GPUs in a GPU family: `s1.4x` has 4 vCPUs and 16 GiB, and `g1-b300.2x` two B300 GPUs. Read ids from this list rather than building them; sizes and families can be added at any time. GPU sizes, which carry `gpu`, are offered only through a reservation (`POST /v1/reservations`) and never on demand. `nodePool` marks the sizes a managed Kubernetes node pool can run.
List capacity GET
Reports, for each location, TEE and size, and each of the size's `purchaseOptions`, a coarse capacity level and the largest `count` one create with that purchase option could get now, at most 16. For `reservation` it is the most one create against one of your org's reservations there whose window is open could get, on its unused GPUs. `maxCount` stays within your credential's limits, and for `on-demand` within your org's quotas too. The API counts room as a create does, on the same hosts with the same vCPUs, memory, GPUs and instance slots, so a create of at most `maxCount` fits unless its image, disks or addresses do not, such as an image that has not booted at the size on those hosts. A create of more is refused, and its problem document says why and how many would have fit: `quota_exceeded` for a quota or limit, `reservation_exhausted` or `reservation_not_active` for a reservation, and `insufficient_capacity` for room. The answer is advisory: room can be taken a moment later, and comes back as instances stop and reservations end.