OpsMill
OpsMill is the company behind Infrahub, an open-source, graph-based infrastructure data management platform that unifies a source of truth for network, data center, and cloud automation. Infrahub combines a flexible, extensible schema, native version control with branching and merging, and unified Git + graph-database storage, then exposes that data through a GraphQL API, a REST API, a Python SDK, the infrahubctl CLI, a web UI, and a Model Context Protocol (MCP) server so both automation pipelines and AI agents can query, propose, and review infrastructure changes with peer review and CI workflows built in.
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 OpsMill the way a machine reads it — 20 machine-readable artifacts across 16 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 — OpsMill scores 51.0/100 (developing), with a separate agent-readiness read of 65/100 (agent native). 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 OpsMill
Each block below is one kind of artifact we hold for OpsMill. 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 16
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.
Infrahub GraphQL API
The GraphQL API is Infrahub's primary interface, auto-generated from core and user-defined schema models, supporting branch-aware queries, time-travel (global branch), mutations...
OpsMill Artifact API
The Artifact API from OpsMill — 2 operation(s) for artifact.
OpsMill Auth API
The Auth API from OpsMill — 4 operation(s) for auth.
OpsMill Config API
The Config API from OpsMill — 1 operation(s) for config.
OpsMill Diff API
The Diff API from OpsMill — 2 operation(s) for diff.
OpsMill File API
The File API from OpsMill — 1 operation(s) for file.
OpsMill Info API
The Info API from OpsMill — 1 operation(s) for info.
OpsMill Menu API
The Menu API from OpsMill — 1 operation(s) for menu.
OpsMill Oauth2 API
The Oauth2 API from OpsMill — 2 operation(s) for oauth2.
OpsMill Oidc API
The Oidc API from OpsMill — 2 operation(s) for oidc.
OpsMill Query API
The Query API from OpsMill — 1 operation(s) for query.
OpsMill Schema API
The Schema API from OpsMill — 6 operation(s) for schema.
OpsMill Schema.graphql API
The Schema.graphql API from OpsMill — 1 operation(s) for schema.graphql.
OpsMill Storage API
The Storage API from OpsMill — 6 operation(s) for storage.
OpsMill Telemetry API
The Telemetry API from OpsMill — 1 operation(s) for telemetry.
OpsMill Transform API
The Transform API from OpsMill — 2 operation(s) for transform.
Scroll within the panel for all 16 ·
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.
opsmill-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.
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 OpsMill — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
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 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/opsmill · machine-readable index on apis.io