Groundwork Open Source
GroundWork Open Source, Inc. builds GroundWork Monitor, an open-source-based IT and network monitoring platform for hybrid infrastructure, assembling Nagios Core, Telegraf, InfluxDB, and Grafana into a unified availability, event, and metrics monitoring product. Its integration layer, the Transit Connection Generator (TCG), exposes a Controller REST API and a Go SDK for feeding host/ service inventory, metrics, alert events, and downtime windows into the GroundWork Foundation server. The platform is self-hosted; all source lives on GitHub under the gwos organization (TCG, Nagios Core, Grafana, and Telegraf forks). Surfaced as a portfolio company of Canaan Partners and enriched here from its live GitHub org and published Swagger 2.0 API specification.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Groundwork Open Source the way a machine reads it — 10 machine-readable artifacts across 8 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 — Groundwork Open Source scores 28.4/100 (emerging), with a separate agent-readiness read of 51/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 Groundwork Open Source
Each block below is one kind of artifact we hold for Groundwork Open Source. 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 8
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.
Groundwork Open Source agent API
The agent API from Groundwork Open Source — 8 operation(s) for agent.
Groundwork Open Source alert API
The alert API from Groundwork Open Source — 3 operation(s) for alert.
Groundwork Open Source connector API
The connector API from Groundwork Open Source — 8 operation(s) for connector.
Groundwork Open Source downtimes API
The downtimes API from Groundwork Open Source — 2 operation(s) for downtimes.
Groundwork Open Source event API
The event API from Groundwork Open Source — 3 operation(s) for event.
Groundwork Open Source inventory API
The inventory API from Groundwork Open Source — 1 operation(s) for inventory.
Groundwork Open Source metric API
The metric API from Groundwork Open Source — 1 operation(s) for metric.
Groundwork Open Source metrics API
The metrics API from Groundwork Open Source — 1 operation(s) for metrics.
Scroll within the panel for all 8 ·
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.
groundwork-open-source-mcp.yml
MCP SERVERSecurity 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.
Resources
Every other property we hold for Groundwork Open Source — 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.
Documentation 3
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 1
Authentication, authorization, and security posture
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/groundwork-open-source · machine-readable index on apis.io