# Scale Computing

> Scale Computing builds SC//Platform — SC//HyperCore, a self-healing KVM-based virtualization and
> storage OS running on clustered appliance nodes, and SC//Fleet Manager, a cloud console that
> monitors, updates and orchestrates thousands of distributed HyperCore clusters, VMs and
> containerized edge applications. Two REST surfaces: an on-appliance HyperCore API at /rest/v1 on
> each clustered node, and a public API-key-authenticated cloud API at api.scalecomputing.com.

Generated by API Evangelist on 2026-08-26 from apis.yml and the artifacts in this repository.
Scale Computing does not publish an llms.txt of its own (probed www.scalecomputing.com/llms.txt,
fleet.scalecomputing.com/llms.txt and api.scalecomputing.com/llms.txt on 2026-08-26 — the first two
return the site catch-all page, the third returns 404).

## APIs

- [SC//Fleet Manager API](https://api.scalecomputing.com/api/v2): Public cloud REST API. 14 operations
  over clusters, virtual machines, cluster conditions, organization activity, metrics and API keys.
  Base URL https://api.scalecomputing.com. Auth: `api-key` request header, issued from
  https://fleet.scalecomputing.com/organization/settings. Every endpoint is role-restricted.
- [Scale Computing Platform Core API](https://api.scalecomputing.com/swagger.json): Undocumented v1
  control plane on the same host — cluster registration and command dispatch, node registration and
  certificate issuance, zero-touch staged cluster provisioning, organization/role/user management,
  Salesforce account sync. 56 operations, no summaries, no descriptions, no human-facing reference.
- [SC//HyperCore REST API](https://github.com/ScaleComputing/RestAPIExamples): On-appliance API served
  by each clustered node at /rest/v1 for VM, disk, network, snapshot, replication and cluster
  automation. Base URL is the customer's own node address; its Swagger docs are reachable only from
  inside the customer network at /rest/v1/docs/ or via the Control Panel Support tab.

## Specs

- [SC//Fleet Manager OpenAPI 3.0](https://api.scalecomputing.com/api/v2/openapi.json)
- [Core v1 OpenAPI 3.0](https://api.scalecomputing.com/swagger.json)
- [Fleet Manager Application Manifest JSON Schema (draft-07)](https://github.com/ScaleComputing/kraken-applications/blob/main/docs/schema.json)

## Client libraries

- [scale_computing.hypercore Ansible collection](https://galaxy.ansible.com/ui/repo/published/scale_computing/hypercore/) — official, v1.6.1 (2025-03-17)
- [ScaleComputing/hypercore Terraform provider](https://registry.terraform.io/providers/ScaleComputing/hypercore/latest) — official, v1.4.0 (2026-02-09)
- [RestAPIExamples](https://github.com/ScaleComputing/RestAPIExamples) — official example scripts, no registry release

There is no first-party SDK in any language, and no client library for the SC//Fleet Manager cloud API.

## Docs

- [Scale Computing](https://www.scalecomputing.com/)
- [SC//Fleet Manager](https://www.scalecomputing.com/sc-fleet-manager)
- [SC//HyperCore / SC//Platform](https://www.scalecomputing.com/sc-platform)
- [HyperCore Ansible Collection documentation](https://scalecomputing.github.io/HyperCoreAnsibleCollection/)
- [GitHub organization](https://github.com/ScaleComputing)
- [Support](https://www.scalecomputing.com/support)
- [Community (login required)](https://community.scalecomputing.com/)
- [Blog](https://www.scalecomputing.com/blog)
- [Pricing (quote-only)](https://www.scalecomputing.com/pricing)
- [Legal / EULAs](https://www.scalecomputing.com/legal)
- [Privacy Policy](https://www.scalecomputing.com/privacy-policy)

## What is NOT published

Verified absent as of 2026-08-26, so an agent does not go looking:

- No MCP server, no A2A agent card, no llms.txt, no security.txt, no api-catalog.
- No status page (status.scalecomputing.com does not resolve; the spec's GET /health 404s).
- No changelog or release notes for either REST API; no deprecation or versioning policy; no SLA.
- No documented rate limits and no rate-limit response headers.
- No idempotency mechanism; no sandbox or test environment; no free trial or self-serve API signup.
- No GraphQL, gRPC/Protobuf, SOAP/WSDL, AsyncAPI, or webhook surface.
- No published error-code registry; the v2 spec declares HTTP 400 and nothing else.