# Oxide

**Canonical:** https://apis.io/providers/oxide-computer/  
**Website:** https://oxide.computer  
**APIs profiled:** 1

Oxide Computer Company builds a rack-scale cloud computer: integrated server sleds (Gimlet), a rack-level switch (Sidecar), Oxide's own illumos distribution (Helios), the Propolis/bhyve hypervisor and the Crucible distributed block store, all driven by a single control plane called Nexus. Nexus exposes the Oxide Region API, a 315-operation OpenAPI 3.0.3 REST contract covering silos, projects, instances, disks, snapshots, images, VPCs, subnets, firewall rules, floating and ephemeral IPs, IP pools, affinity groups, alerts and webhook receivers, audit log, metrics/OxQL, hardware inventory, BGP/BFD networking, SAML and SCIM identity, support bundles and system update. Because the product is a rack a customer owns, the API is served from the customer's own control-plane domain rather than a vendor-hosted endpoint. Oxide publishes first-party Rust, TypeScript and Go SDKs, an `oxide` CLI, a Terraform provider and a Packer plugin, and develops essentially the entire stack in the open on GitHub.

## Kin Score — 42.6 / 100 (developing)

Scored 2026-09-02 under rubric 0.18.0. Trend: flat (+0.9 from 41.7).

| Facet | Score |
|---|---|
| Discoverability | 75.9 |
| Contract Quality | 51.7 |
| Governance | 4.5 |
| Contract Governance | 4.5 |
| Operational Transparency | 36.8 |
| Developer Ergonomics | 73.2 |
| Commercial Clarity | 10.5 |
| Access Clarity | 10.5 |

## Agent readiness — 26.1 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | bearer |
| Idempotency | no |
| Error Semantics | documented |
| OpenAPI Examples | no |
| Rate Limit Signal | documented |
| Event Surface Described | yes |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |

## Access

Self-serve signup — onboarding: self-serve, pricing: unknown, trial: no (confidence: medium).

## APIs (30)

- **Oxide Affinity API** — Anti-affinity groups give control over instance placement.
- **Oxide Console Auth API** — API for console authentication
- **Oxide Current User API** — Information pertaining to the current user.
- **Oxide Disks API** — Virtual disks are used to store instance-local data which includes the operating system.
- **Oxide Experimental API** — Experimental, unstable interfaces, primarily for use by Oxide personnel
- **Oxide External Subnets API** — External subnets that can be attached to instances.
- **Oxide Floating Ips API** — Floating IPs allow a project to allocate well-known IPs to instances.
- **Oxide Images API** — Images are read-only virtual disks that may be used to boot virtual machines.
- **Oxide Instances API** — Virtual machine instances are the basic unit of computation. These operations are used for provisioning, controlling, and destroying instances.
- **Oxide Ip Pools API** — IP pools are collections of external IPs that can be allocated and attached to instances.
- **Oxide Login API** — Authentication endpoints
- **Oxide Metrics API** — Silo-scoped metrics
- **Oxide Policy API** — System-wide IAM policy
- **Oxide Projects API** — Projects are a grouping of associated resources such as instances and disks within a silo for purposes of billing and access control.
- **Oxide Silos API** — Silos represent a logical partition of users and resources.
- **Oxide Snapshots API** — Snapshots of virtual disks at a particular point in time.
- **Oxide Subnet Pools API** — Subnet pools are collections of external subnets that can be allocated and attached to instances.
- **Oxide System/alerts API** — Alerts deliver notifications for events that occur on the Oxide rack
- **Oxide System/audit Log API** — These endpoints relate to audit logs.
- **Oxide System/hardware API** — These operations pertain to hardware inventory and management. Racks are the unit of expansion of an Oxide deployment. Racks are in turn composed of sleds, switches, power suppl...
- **Oxide System/ip Pools API** — IP pools are collections of external IPs. Linking a pool to a silo makes it available for allocation by users in that silo.
- **Oxide System/metrics API** — Metrics provide insight into the operation of the Oxide deployment. These include telemetry on hardware and software components that can be used to understand the current state ...
- **Oxide System/networking API** — This provides rack-level network configuration.
- **Oxide System/silos API** — Silos represent a logical partition of users and resources.
- **Oxide System/status API** — Endpoints related to system health
- **Oxide System/subnet Pools API** — Subnet pools are collections of external subnets. Linking a pool to a silo makes it available for allocation by users in that silo.
- **Oxide System/support Bundles API** — Support bundles collect debugging information from the rack for use by Oxide support.
- **Oxide System/update API** — Upload and manage system updates
- **Oxide Tokens API** — API clients use device access tokens for authentication.
- **Oxide Vpcs API** — Virtual Private Clouds (VPCs) provide isolated network environments for managing and deploying services.

## Security (3)

- **Oxide Computer Authentication** — 4 schemes
- **Oxide Computer Domain Security** — TLSv1.3 · HSTS · DMARC
- **Oxide Computer Vulnerability Disclosure** — security.txt · contact published

## Plans (1)

- **Oxide Computer Plans Pricing**

## Tags

Cloud Computing, Infrastructure, Compute, Virtualization, Networking, Storage, Hardware, On-Premise, Private Cloud, Open-Source

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/oxide-computer/). Scores are computed from the provider's own public artifacts under a published rubric.