Skip to main content
Use this page to track changes to the Compute API that may affect scripts, tools, or integrations.

​
Current API version

Production base URL: https://api.hivecompute.ai/v1 Staging base URL: https://staging-api.hivecompute.ai/v1 The current release contains eight public endpoints. The endpoint reference shows the current request and response details.

​
Latest changes

​

​
API surface finalized for release

Changed
  • Production base URL is now https://api.hivecompute.ai/v1.
  • Staging is available at https://staging-api.hivecompute.ai/v1.
  • Region values are UAE, FR, and US.
  • Instance logs are returned newest first. entries[0] is the most recent line.
  • Start, stop, and terminate can return 409 Conflict with error code CONFLICT when the requested action conflicts with the current lifecycle state.
  • 500 responses use the generic message An internal error occurred. Clients should use error.code, not error.message, for program logic.
  • 429 responses include Retry-After and use the standard error envelope.
Removed from this release
  • POST /ssh-keys
  • GET /ssh-keys/{id}
SSH-key operations are not backed by the released public API and will return in a later release.
​

​
Public API documentation prepared

Initial documentation covered instance lifecycle operations, logs, regions, presets, and planned SSH-key operations. The release surface was subsequently narrowed and finalized in the August update above.

​
Current endpoints

​
What counts as a breaking change

A breaking change may require you to update code that already works. Examples include removing an endpoint or field, changing a field type, changing authentication behavior, or making an existing request parameter required.
Don’t rely on undocumented fields or behavior. Build integrations against the published API reference.

​
How to stay compatible

  • Use the versioned base URL shown in the docs.
  • Build logic around documented fields and error.code values.
  • Treat cursors as opaque.
  • Respect Retry-After on 429 responses.
  • Check instance state before retrying lifecycle actions.
  • Review this changelog when integration behavior changes unexpectedly.