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 — 97 machine-readable artifacts across 24 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 58.1/100 (strong), with a separate agent-readiness read of 24/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Chef Software's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/chef-software/"
title="Chef Software on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/chef-software.svg"
alt="Chef Software Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/chef-software/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/chef-software/"
title="Chef Software on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/chef-software/card.svg"
alt="Chef Software Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 ·
Postman Collections 30
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 30 ·
Open Collections 31
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONScroll within the panel for all 31 ·
Event 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 5
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 2
The organization behind the API
Other 3
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
This is an independent, third-party profile of Chef Software, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.