Chef Software
Chef Software is the DevOps automation company behind Chef Infra, Chef InSpec, Chef Habitat, and Chef Automate, now part of Progress Software. Chef pioneered infrastructure-as-code, letting teams define, deploy, and continuously enforce the configuration, compliance, and security posture of servers and applications across data centers and cloud at any scale. Chef Automate exposes a REST API (generated from gRPC service definitions via grpc-gateway) for managing compliance reporting, node management, configuration management, secrets, data feeds, event feeds, IAM (users, teams, tokens, policies, rules), and the application service catalog. Authentication is via API tokens presented in the api-token HTTP header. Chef also ships a deep open-source ecosystem of Ruby client tooling (chef-client, InSpec, Ohai, Berkshelf, chef-cli, knife) distributed on RubyGems, all developed in the open on the chef GitHub org.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Chef Software the way a machine reads it — 37 machine-readable artifacts across 30 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 — Chef Software scores 61.5/100 (strong), with a separate agent-readiness read of 71/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 Chef Software
Each block below is one kind of artifact we hold for Chef Software. 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 30
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.
Chef Software ApplicationsService API
The ApplicationsService API from Chef Software — 2 operation(s) for applicationsservice.
Chef Software Authorization API
The Authorization API from Chef Software — 2 operation(s) for authorization.
Chef Software Cds API
The Cds API from Chef Software — 4 operation(s) for cds.
Chef Software ChefIngester API
The ChefIngester API from Chef Software — 6 operation(s) for chefingester.
Chef Software Comp_Assets API
The Comp_Assets API from Chef Software — 4 operation(s) for comp_assets.
Chef Software ConfigMgmt API
The ConfigMgmt API from Chef Software — 23 operation(s) for configmgmt.
Chef Software DatafeedService API
The DatafeedService API from Chef Software — 6 operation(s) for datafeedservice.
Chef Software DataLifecycle API
The DataLifecycle API from Chef Software — 15 operation(s) for datalifecycle.
Chef Software EventFeedService API
The EventFeedService API from Chef Software — 4 operation(s) for eventfeedservice.
Chef Software hidden API
The hidden API from Chef Software — 5 operation(s) for hidden.
Chef Software InfraProxy API
The InfraProxy API from Chef Software — 36 operation(s) for infraproxy.
Chef Software JobScheduler API
The JobScheduler API from Chef Software — 4 operation(s) for jobscheduler.
Chef Software JobsService API
The JobsService API from Chef Software — 4 operation(s) for jobsservice.
Chef Software NodeManagerService API
The NodeManagerService API from Chef Software — 9 operation(s) for nodemanagerservice.
Chef Software NodesService API
The NodesService API from Chef Software — 7 operation(s) for nodesservice.
Chef Software policies API
The policies API from Chef Software — 6 operation(s) for policies.
Chef Software ProfilesService API
The ProfilesService API from Chef Software — 5 operation(s) for profilesservice.
Chef Software projects API
The projects API from Chef Software — 2 operation(s) for projects.
Chef Software ReportingService API
The ReportingService API from Chef Software — 12 operation(s) for reportingservice.
Chef Software ReportManagerService API
The ReportManagerService API from Chef Software — 1 operation(s) for reportmanagerservice.
Chef Software retention API
The retention API from Chef Software — 4 operation(s) for retention.
Chef Software roles API
The roles API from Chef Software — 2 operation(s) for roles.
Chef Software rules API
The rules API from Chef Software — 4 operation(s) for rules.
Chef Software SecretsService API
The SecretsService API from Chef Software — 3 operation(s) for secretsservice.
Chef Software service_groups API
The service_groups API from Chef Software — 9 operation(s) for service_groups.
Chef Software StatsService API
The StatsService API from Chef Software — 6 operation(s) for statsservice.
Chef Software teams API
The teams API from Chef Software — 6 operation(s) for teams.
Chef Software tokens API
The tokens API from Chef Software — 2 operation(s) for tokens.
Chef Software users API
The users API from Chef Software — 3 operation(s) for users.
Chef Software UserSettingsService API
The UserSettingsService API from Chef Software — 1 operation(s) for usersettingsservice.
Scroll within the panel for all 30 ·
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.
chef-software-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Chef Software Data Feed Webhooks
ASYNCAPISecurity 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.
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 Chef Software — 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 4
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 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/chef-software · machine-readable index on apis.io