Incus
Incus is a modern open source system container and virtual machine manager maintained by LinuxContainers.org as a community-led fork of Canonical's LXD. It provides a unified experience for running and managing system containers and VMs across single hosts and clusters, with image-based deployment, live migration, snapshots, projects, and a comprehensive RESTful API for automation and tooling integration.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Incus the way a machine reads it — 29 machine-readable artifacts across 22 APIs, 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 — Incus scores 36.1/100 (thin), with a separate agent-readiness read of 39/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Incus
Each block below is one kind of artifact we hold for Incus. 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 22
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.
Incus certificates API
The certificates API from Incus — 4 operation(s) for certificates.
Incus cluster API
The cluster API from Incus — 7 operation(s) for cluster.
Incus cluster-groups API
The cluster-groups API from Incus — 3 operation(s) for cluster-groups.
Incus images API
The images API from Incus — 14 operation(s) for images.
Incus instances API
The instances API from Incus — 28 operation(s) for instances.
Incus Metadata API
The Metadata API from Incus — 1 operation(s) for metadata.
Incus metrics API
The metrics API from Incus — 1 operation(s) for metrics.
Incus network-acls API
The network-acls API from Incus — 4 operation(s) for network-acls.
Incus network-address-sets API
The network-address-sets API from Incus — 3 operation(s) for network-address-sets.
Incus network-allocations API
The network-allocations API from Incus — 1 operation(s) for network-allocations.
Incus network-forwards API
The network-forwards API from Incus — 3 operation(s) for network-forwards.
Incus network-integrations API
The network-integrations API from Incus — 3 operation(s) for network-integrations.
Incus network-load-balancers API
The network-load-balancers API from Incus — 4 operation(s) for network-load-balancers.
Incus network-peers API
The network-peers API from Incus — 3 operation(s) for network-peers.
Incus network-zones API
The network-zones API from Incus — 6 operation(s) for network-zones.
Incus networks API
The networks API from Incus — 5 operation(s) for networks.
Incus operations API
The operations API from Incus — 7 operation(s) for operations.
Incus profiles API
The profiles API from Incus — 3 operation(s) for profiles.
Incus projects API
The projects API from Incus — 5 operation(s) for projects.
Incus server API
The server API from Incus — 5 operation(s) for server.
Incus storage API
The storage API from Incus — 39 operation(s) for storage.
Incus warnings API
The warnings API from Incus — 3 operation(s) for warnings.
Scroll within the panel for all 22 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Incus external REST API
OPEN COLLECTIONPricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Incus Plans Pricing
PLANSRate 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.
Incus Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Incus Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Incus API Rules
SPECTRALSecurity Posture 1
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Incus — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/incus · machine-readable index on apis.io