Oxide
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.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Oxide the way a machine reads it — 36 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Oxide scores 41.7/100 (developing), with a separate agent-readiness read of 26/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Oxide's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/oxide-computer/"
title="Oxide on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/oxide-computer.svg"
alt="Oxide Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/oxide-computer/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/oxide-computer/"
title="Oxide on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/oxide-computer/card.svg"
alt="Oxide Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Oxide
Each block below is one kind of artifact we hold for Oxide. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 30
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
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.
Scroll within the panel for all 30 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Oxide Computer Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Oxide Computer Alerts Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Oxide — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/oxide-computer · machine-readable index on apis.io
This is an independent, third-party profile of Oxide, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.