Kace

KACE is the endpoint and systems management product line from Quest Software, originally founded in 2003 as KACE Networks (backed by Norwest Venture Partners, Sigma Partners, and Focus Ventures), acquired by Dell in 2010, and now sold as Quest KACE. The portfolio centers on the KACE Systems Management Appliance (SMA) for inventory, patching, software distribution, scripting, and service desk; the KACE Systems Deployment Appliance (SDA) for OS imaging and provisioning; and KACE Cloud for mobile device management and modern endpoint management. The KACE SMA ships a REST API (JSON and XML) that lets administrators programmatically manage assets, inventory, managed installations, scripting, users, and service-desk tickets on the customer-hosted appliance. This profile enriches the original Norwest portfolio lead with the real Quest KACE identity and its documented API surface.

Kace is listed with 1 API on the APIs.io network. Tagged areas include Company, Endpoint Management, Systems Management, IT Asset Management, and Patch Management.

Kace’s developer surface includes documentation, API reference, support, authentication, and 7 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

11.6/100 emerging ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Endpoint Management Systems Management IT Asset Management Patch Management Service Desk Device ManagementQuest Software

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 11.6/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.8 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.9 / 11

Contract Governance 0.5 / 10

Discoverability 5.5 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/kace/"><img src="https://apis.io/badge/kace/card.svg" alt="Kace on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 16.7 — up to +16.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/kace/apis.yml: open an issue on github.com/api-evangelist/kace to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Device Management (MDM, UEM, mobile threat defense)	standard	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

KACE Systems Management Appliance (SMA) API

REST API for the KACE Systems Management Appliance. Authenticated KACE SMA users can manage appliance data across the Asset, Inventory, Managed Install, Scripting, User, and Ser...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Kace Authentication

session · 1 scheme

SECURITY

Kace Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

Deprecation

Deprecation

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: kace
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/kace.png
name: Kace
description: KACE is the endpoint and systems management product line from Quest Software, originally founded in 2003 as KACE
  Networks (backed by Norwest Venture Partners, Sigma Partners, and Focus Ventures), acquired by Dell in 2010, and now sold
  as Quest KACE. The portfolio centers on the KACE Systems Management Appliance (SMA) for inventory, patching, software distribution,
  scripting, and service desk; the KACE Systems Deployment Appliance (SDA) for OS imaging and provisioning; and KACE Cloud
  for mobile device management and modern endpoint management. The KACE SMA ships a REST API (JSON and XML) that lets administrators
  programmatically manage assets, inventory, managed installations, scripting, users, and service-desk tickets on the customer-hosted
  appliance. This profile enriches the original Norwest portfolio lead with the real Quest KACE identity and its documented
  API surface.
url: https://raw.githubusercontent.com/api-evangelist/kace/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- norwest-venture-partners
x-tier: enriched
x-tier-reason: acquired-by-dell-2010-now-quest-kace
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Endpoint Management
- Systems Management
- IT Asset Management
- Patch Management
- Service Desk
- Device Management
- Quest Software
apis:
- name: KACE Systems Management Appliance (SMA) API
  description: REST API for the KACE Systems Management Appliance. Authenticated KACE SMA users can manage appliance data
    across the Asset, Inventory, Managed Install, Scripting, User, and Service Desk modules. Requests and responses support
    JSON and XML (selected via Accept / Content-Type), with API routing controlled by an x-kace-api-version header and query
    features for filtering, sorting, paging, shaping, and counting. The API runs on the customer-hosted appliance, so the
    base URL is the local appliance host (https://<kace_sma_host>/ams/); there is no shared public production host.
  humanURL: https://support.quest.com/technical-documents/kace-systems-management-appliance/15.0/api-reference-guide
  properties:
  - type: APIReference
    url: https://support.quest.com/technical-documents/kace-systems-management-appliance/15.0/api-reference-guide
  - type: Authentication
    url: https://raw.githubusercontent.com/api-evangelist/kace/refs/heads/main/authentication/kace-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/kace-domain-security.yml
- type: Website
  url: https://www.quest.com/kace/
- type: DeveloperPortal
  url: https://www.quest.com/kace/
- type: Documentation
  url: https://support.quest.com/kace-systems-management-appliance/technical-documents
- type: APIReference
  url: https://support.quest.com/technical-documents/kace-systems-management-appliance/15.0/api-reference-guide
- type: Support
  url: https://support.quest.com/kace-systems-management-appliance
- type: Authentication
  url: https://raw.githubusercontent.com/api-evangelist/kace/refs/heads/main/authentication/kace-authentication.yml
- type: Lifecycle
  url: lifecycle/kace-lifecycle.yml
- type: Deprecation
  url: https://support.quest.com/kb/4268357/kace-software-product-support-lifecycle-policy
- type: Conformance
  url: conformance/kace-conformance.yml
- type: LLMsTxt
  url: llms/kace-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence
x-parent: quest-software-inc
x-relationship: product

Kace API — frequently asked questions

Does Kace have an API?

Yes. APIs.io lists 1 API from Kace, including KACE Systems Management Appliance (SMA) API.

How do I authenticate with the Kace API?

Kace uses bearer-token authentication (session · 1 scheme). The details are profiled on APIs.io as Kace Authentication.

Is the Kace API ready for AI agents?

Kace has a Kin Score of 11.6 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/kace"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/kace/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/kace/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.