Billing and compute quotes
Review prices before work starts, track held credit, and explicitly accept new usage policies.
Accept the quoted operation
Request a quote with the product, organization, location, resources, maximum runtime and network cap. The response gives normalized allocation, billing currency, total hourly rate, minimum started-runtime charge, maximum credit hold, pricing version, exchange rate and expiry. Monetary fields use integer microcents: 100,000,000 units equal one unit of the named currency. EUR quotes are already converted.
After reviewing the quote, send its ID as accepted_quote_id with the same creation parameters. Acceptance is bound to the organization and can create only one resource. Expired or changed quotes require a new review. Reusing the same creation idempotency key retries that operation; do not use a new key to recover an uncertain execution.
Quote creation alone does not reserve credit. Admission reserves the maximum before accepting paid work, and settlement releases the unused portion. Shared credit, spend limits, authorization, rate limits and physical capacity still apply. There is no per-organization resource-count quota.
| Method | Path | Purpose |
|---|---|---|
| POST | /control/v1/orgs/{org_id}/compute-quotes | Create a five-minute compute quote without reserving credit |
| GET | /control/v1/orgs/{org_id}/usage-policy | Read current allowances, inventory, estimate and accepted version |
| POST | /control/v1/orgs/{org_id}/usage-policy/accept | Owner acceptance of a qualified policy and unexpired estimate |
Availability and placement
Omitting a location selects the current product default from ListLocations. Its capabilities report which locations accept new resources and which still support existing ones. An explicit closed location fails; it is never silently moved. Existing resources retain their location, volumes and billing. The console shows a quote before creation and binds the operation to that quote's location. See data residency for processing locations.
Agent Host dry runs return spec.compute_quote and an admission assessment with availability, reason and check time. The preview reserves no capacity; real admission checks it again atomically. The existing spec.billing_quote remains available in the account's currency.
Compute is available in US East. Its quote contract covers us-1 sandboxes, jobs and Agent Hosts, with explicit acceptance required. A price or published API method does not enable a product. Use the quote's available field and current location availability.
The US East policy permits metered public HTTPS on port 443, capped per execution. Both forwarded directions count against the cap. Private destinations and direct network bypass are disallowed; platform image and control traffic are excluded. A zero cap disables external access. For Agent Hosts the allowance renews every five minutes and includes public ingress; its quote separately states persistent disk pricing and the initial startup hold. Allocated US East disk is billed during setup and while paused until deletion.
Data and build charges require acceptance
New data and build charges are in shadow verification and are not active. The Billing console displays the policy version, free allowances, current usage, remaining units, overage rates and inventory timestamp. An organization owner must accept an unexpired estimate after metering is qualified. Existing data and past usage are never charged retroactively.
Objects including historical versions, Git/LFS and custom build layers share a retained-data allowance. Provisioned EU Agent Host volumes have a separate allowance, including paused volumes. US East Agent Host disk is covered by its explicit compute quote and is not charged again under this inactive policy. Custom builds and EU downloads have UTC-calendar-month allowances without rollover. EU uploads and storage/Git API operations are included under existing rate and capacity controls. Platform copies, backups and base images are excluded; backing storage and internal transfers are not counted twice.
An approved account receives one allowance allocation in its first organization. Adding owners or organizations does not stack allowances. The console shows the applicable rates and version; model prices and the existing starter credit are unchanged by this policy.
Retention at exhausted credit
Under the accepted usage policy, exhausted credit or spend limits block paid writes and builds and pause hosts with unfunded paid volumes. Stored data is retained read-only without automatic deletion or unpaid debt. Deletion remains available; downloads require remaining free allowance or credit. Funding restores paid write eligibility; paused hosts require explicit resume. Stale meters block new paid growth until usage is verified.
Storage estimates project the current allocation over 720 hours; they are not a monthly cap. Build and transfer charges depend on actual usage. Queue time and confirmed platform-caused failures are free; customer-caused build failures count.
Failures, cancellation and recovery
HTTP 402 with insufficient_balance or spend_limit_reached means admission could not fund the requested work. Top up or adjust the relevant spend limit before retrying. A quote is price consent, not a guarantee of funding or capacity.
compute_quote_expired_or_changed and compute_quote_parameters_changed require a fresh quote and review. usage_policy_not_qualified means new policy charging cannot be activated. usage_policy_estimate_expired requires a new estimate. Do not automatically accept a replacement quote or policy.
For US East jobs, cancellation requests a stop; read terminal run state before assuming completion. Queue and setup time are free. Once execution starts, cancellation and application failures pay for runtime subject to the quoted minimum. Confirmed platform failures waive the operation including network. Work with uncertain completion is not automatically replayed.