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 — 25 machine-readable artifacts across 17 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 — Huntress scores 55.7/100 (developing), with a separate agent-readiness read of 78/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 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 ·
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.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.
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