Puppet
Puppet (Perforce Puppet, formerly Puppet Labs) is an infrastructure automation and configuration-management platform used by more than 40,000 organizations to manage servers, networks, cloud, and edge infrastructure through desired-state, policy-driven automation. Its products include Puppet Enterprise, Puppet Core, the Bolt orchestration tool, and the Puppet Forge module registry. The public Puppet Forge v3 API provides RESTful access to the modules, releases, users, and release plans published on Forge; Puppet Enterprise additionally exposes REST APIs for orchestration, node classification, RBAC, and PuppetDB querying. Puppet was acquired by Perforce Software in 2022.
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 Puppet the way a machine reads it — 8 machine-readable artifacts across 4 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 — Puppet scores 44.2/100 (thin), with a separate agent-readiness read of 22/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.
How we profile Puppet
Each block below is one kind of artifact we hold for Puppet. 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 4
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.
Puppet Module Operations API
The Module Operations API from Puppet — 2 operation(s) for module operations.
Puppet Release Operations API
The Release Operations API from Puppet — 5 operation(s) for release operations.
Puppet Search Filter Operations API
The Search Filter Operations API from Puppet — 2 operation(s) for search filter operations.
Puppet User Operations API
The User Operations API from Puppet — 2 operation(s) for user operations.
Security Posture 4
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 Puppet — 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 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
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/puppet-labs · machine-readable index on apis.io