Vers
Vers is "git for running compute" — a branchable microVM platform from HD Research (hdresearch) that lets you fork a live virtual machine (memory, processes, sockets and all) in roughly 258 microseconds, commit its state as an immutable content-addressable snapshot, and restore or branch that snapshot anywhere. Built for AI agent swarms, parallel scenario and database-state testing, CI preview environments, and time-travel debugging, Vers exposes a 63-operation Orchestrator Control Plane API (OpenAPI 3.1) behind a bearer API key, plus a git-style CLI, official SDKs for nine languages, and two Model Context Protocol servers so coding agents can drive compute directly.
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 Vers the way a machine reads it — 15 machine-readable artifacts across 12 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 — Vers scores 44.2/100 (thin), with a separate agent-readiness read of 60/100 (agent ready). 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 Vers
Each block below is one kind of artifact we hold for Vers. 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 12
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.
Vers commit_tags API
The commit_tags API from Vers — 2 operation(s) for commit_tags.
Vers commits API
The commits API from Vers — 4 operation(s) for commits.
Vers deploy API
The deploy API from Vers — 1 operation(s) for deploy.
Vers domains API
The domains API from Vers — 2 operation(s) for domains.
Vers env_vars API
The env_vars API from Vers — 2 operation(s) for env_vars.
Vers images API
The images API from Vers — 5 operation(s) for images.
Vers keys API
The keys API from Vers — 1 operation(s) for keys.
Vers public_repositories API
The public_repositories API from Vers — 4 operation(s) for public_repositories.
Vers repositories API
The repositories API from Vers — 6 operation(s) for repositories.
Vers System API
The System API from Vers — 1 operation(s) for system.
Vers vm API
The vm API from Vers — 20 operation(s) for vm.
Vers vms API
The vms API from Vers — 2 operation(s) for vms.
Scroll within the panel for all 12 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
vers-mcp.yml
MCP SERVERSecurity Posture 2
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 Vers — 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 3
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 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
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
← All providers · Data indexed from github.com/api-evangelist/vers · machine-readable index on apis.io