JAMF
Jamf is the standard in managing and securing Apple devices at scale for business, education, and government. Its cloud platform pairs Apple device management (MDM), identity, and endpoint security with a broad developer surface: the modern Jamf Pro API (OpenAPI 3.0, bearer-token and OAuth client-credential API Roles & Clients), the long-standing Classic API (/JSSResource, XML/JSON), the new unified Platform API Gateway (Blueprints, Compliance Benchmarks, Device Management Actions), plus the Jamf School, Jamf Protect, and Jamf Security APIs. Jamf publishes an llms.txt developer index, a hosted MCP server for documentation and code generation, a webhooks event catalog, and a trust center enumerating SOC 2, ISO 27001/27701, PCI DSS, HIPAA, GDPR, and NIST 800-53 posture.
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 JAMF the way a machine reads it — 9 machine-readable artifacts across 3 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 — JAMF scores 57.6/100 (developing), 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 JAMF
Each block below is one kind of artifact we hold for JAMF. 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 3
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.
Jamf Pro API
The modern Jamf Pro API, built on the OpenAPI 3.0 standard, for programmatically managing computers, mobile devices, policies, groups, inventory, and configuration on a Jamf Pro...
Jamf Pro Classic API
The long-standing Classic API, the original resource for programmatically interacting with Jamf Pro, located at /JSSResource on each instance. Supports XML and JSON payloads and...
Jamf Platform API Gateway
A single, unified gateway to access any combination of Jamf APIs — Blueprints, Compliance Benchmarks, Device Management Actions, Declaration Reporting, Devices, and Device Group...
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.
jamf-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.
Jamf 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.
Jamf Trust Center
SOC 2 Type 1, SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 27001 SoA, ISO/IEC 27701, PCI DSS, HIPAA, GDPR, CSA STAR, NIST 800-53 Rev. 5, Cyber Essentials, EU-US Data Privacy Framework, ...
SECURITYResources
Every other property we hold for JAMF — 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 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/jamf · machine-readable index on apis.io