Huntress
Huntress is a managed cybersecurity platform built for small and mid-sized businesses and the MSPs/MSSPs that serve them, pairing purpose-built software with a human-powered 24/7 Security Operations Center (SOC). Its products span Managed EDR (including macOS and Managed Microsoft Defender), Managed ITDR for Microsoft 365 identities, Managed SIEM, and Managed Security Awareness Training. The Huntress REST API (api.huntress.io/v1) gives partners programmatic access to accounts, organizations, agents, incident reports, remediations, escalations, platform actions, signals, external recon, billing and reseller subscriptions, plus a SIEM ES|QL query endpoint — secured with HTTP Basic API keys, cursor-paginated, with real-time webhooks and an official remote MCP server for AI agents.
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 Huntress the way a machine reads it — 44 machine-readable artifacts across 1 API, 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 — Huntress scores 51.1/100 (developing), with a separate agent-readiness read of 56/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. 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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Huntress'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/huntress/"
title="Huntress on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/huntress.svg"
alt="Huntress Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/huntress/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/huntress/"
title="Huntress on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/huntress/card.svg"
alt="Huntress 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 Huntress
Each block below is one kind of artifact we hold for Huntress. 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 17
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.
Huntress Accounts API
Operations about Accounts
Huntress Actor API
Operations about Actors
Huntress Agents API
Operations about Agents
Huntress Escalations API
Operations about Escalations
Huntress External Recon API
Operations about External Recons
Huntress Identities API
Operations about Identities
Huntress Incident Reports API
Operations about Incident Reports
Huntress Invoices API
Operations about Invoices
Huntress Known VPNs API
Operations about Known VPNs
Huntress Organizations API
Operations about Organizations
Huntress Platform Actions API
Operations about Platform Actions
Huntress Reseller API
Operations for Reseller-level API credentials. These are mostly the same endpoints available in the rest of the API. However, the account ID is included in the URL, so that you ...
Huntress SIEM API
Query your SIEM logs programmatically using ES|QL (Elasticsearch Query Language).
Huntress Signals API
Operations about Signals
Huntress Summary Reports API
Operations about Summary Reports
Huntress Unwanted Access Rules API
Operations about Unwanted Access Rules
Huntress Users API
Operations about Users
Scroll within the panel for all 17 ·
Open Collections 19
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 COLLECTIONHuntress API Reference Accounts API
OPEN COLLECTIONHuntress API Reference Accounts Actor API
OPEN COLLECTIONHuntress API Reference Accounts Agents API
OPEN COLLECTIONHuntress API Reference Accounts Escalations API
OPEN COLLECTIONHuntress API Reference Accounts External Recon API
OPEN COLLECTIONHuntress API Reference Accounts Identities API
OPEN COLLECTIONHuntress API Reference Accounts Incident Reports API
OPEN COLLECTIONHuntress API Reference Accounts Invoices API
OPEN COLLECTIONHuntress API Reference Accounts Known VPNs API
OPEN COLLECTIONHuntress API Reference Accounts Organizations API
OPEN COLLECTIONHuntress API Reference Accounts Platform Actions API
OPEN COLLECTIONHuntress API Reference Accounts Reseller API
OPEN COLLECTIONHuntress API Reference Accounts SIEM API
OPEN COLLECTIONHuntress API Reference Accounts Signals API
OPEN COLLECTIONHuntress API Reference Accounts Summary Reports API
OPEN COLLECTIONHuntress API Reference Accounts Unwanted Access Rules API
OPEN COLLECTIONHuntress API Reference Accounts Users API
OPEN COLLECTIONHuntress Webhooks
OPEN COLLECTIONScroll within the panel for all 19 ·
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.
Huntress MCP Server
Huntress operates an official remote MCP server fronting the Huntress API, discoverable via RFC 8414 OAuth Authorization Server metadata and RFC 9728 OAuth Protected Resource me...
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.
Huntress 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Huntress — 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 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 3
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/huntress · machine-readable index on apis.io
This is an independent, third-party profile of Huntress, 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.