Overview - QuantaCloud

The QuantaCloud API lets you programmatically deploy GPU instances, manage SSH keys, and check your account. Everything the console does is available under /api/v1/.

Base URL

https://core.quantacloud.net/api/v1

Authentication

Authenticated endpoints require an API key. Pass it in either header:

# Option 1: X-API-Key header
curl -H "X-API-Key: gpu_live_xxx" https://core.quantacloud.net/api/v1/account/balance

# Option 2: Authorization Bearer
curl -H "Authorization: Bearer gpu_live_xxx" https://core.quantacloud.net/api/v1/account/balance

Create API keys in the console under API Keys. See API Keys for details.

Public catalog endpoints (offers, GPU families, providers) do not require authentication. All other endpoints do.

Error Format

All errors return a consistent JSON envelope:

{
  "error": {
    "code": "not_found",
    "message": "Deployment not found"
  }
}

Error Codes

HTTP Status	Code	Description
400	`bad_request`	Invalid parameters, or a required parameter or header is missing
400	`validation_error`	Validation failed (may include `fields` map)
400	`provider_not_found`	Unknown provider name; the only valid value is `quantacloud`
400	`invalid_request`	Malformed request body
401	—	Missing or invalid API key
402	`insufficient_balance`	Not enough credits
404	`not_found`	Resource not found or not owned by you
405	`method_not_allowed`	Unsupported HTTP method; the `Allow` header lists methods supported at this path
406	—	None of the types in your `Accept` header can be produced; responses are `application/json`. No body is returned.
415	`unsupported_media_type`	Unsupported request content type; use `Content-Type: application/json` for JSON bodies
429	`rate_limited`	Rate limit exceeded
500	`internal_error`	Unexpected server error

Insufficient Balance Example

When you don’t have enough credits to create a deployment, the error includes your current and required balance:

{
  "error": {
    "code": "insufficient_balance",
    "message": "Insufficient balance. Required: $0.5280, available: $0.2000",
    "current_balance": "0.2000",
    "required_balance": "0.5280"
  }
}

Rate Limits

All v1 endpoints share a rate limit of 3,000 requests per 15 minutes per IP address (200 requests per minute on average). The X-RateLimit-Remaining response header shows how many requests you have left. When exceeded, the API returns 429:

{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Please try again later."
  }
}

Monetary Values

All monetary amounts are returned as strings with 4 decimal places (e.g., "0.5280"). This avoids floating-point precision issues.

Timestamps

All timestamps are in ISO 8601 format with UTC timezone (e.g., "2026-09-20T20:12:51.596837Z").

​Base URL

​Authentication

​Error Format

​Error Codes

​Insufficient Balance Example

​Rate Limits

​Monetary Values

​Timestamps

Base URL

Authentication

Error Format

Error Codes

Insufficient Balance Example

Rate Limits

Monetary Values

Timestamps