McAfee (Trellix)
APIs for McAfee Enterprise security products and services. McAfee Enterprise rebranded as Trellix in 2022, but its on-premises and SaaS platforms (ePO, MVISION, ESM, Web Gateway, TIE, DXL) continue to expose REST APIs documented here for centralized security management, threat intelligence, EDR, messaging, and SIEM integration.
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 McAfee (Trellix) the way a machine reads it — 106 machine-readable artifacts across 4 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 — McAfee (Trellix) scores 39.4/100 (developing), with a separate agent-readiness read of 22/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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from McAfee (Trellix)'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/mcafee/"
title="McAfee (Trellix) on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mcafee.svg"
alt="McAfee (Trellix) Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/mcafee/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mcafee/"
title="McAfee (Trellix) on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mcafee/card.svg"
alt="McAfee (Trellix) 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 McAfee (Trellix)
Each block below is one kind of artifact we hold for McAfee (Trellix). 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 26
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.
McAfee Threat Intelligence Exchange (TIE) API
Real-time threat intelligence sharing and reputation services API.
McAfee Data Exchange Layer (DXL) API
Messaging fabric for real-time security data exchange and integration.
McAfee (Trellix) Alarms API
Manage security alarms
McAfee (Trellix) Authentication API
Session authentication and management
McAfee (Trellix) Cases API
Manage incident response cases
McAfee (Trellix) Core API
Core server operations and authentication
McAfee (Trellix) Data Sources API
Manage event data sources
McAfee (Trellix) Detections API
EDR detection events and alerts
McAfee (Trellix) Devices API
Manage ESM device hierarchy
McAfee (Trellix) Events API
Query and retrieve security events
McAfee (Trellix) File Operations API
Import and export configuration files
McAfee (Trellix) Investigations API
Threat investigation workflows and actions
McAfee (Trellix) Lists API
Manage URL and IP lists used in filtering
McAfee (Trellix) Monitoring API
Appliance health and traffic monitoring
McAfee (Trellix) Policies API
Manage and assign security policies
McAfee (Trellix) Policy Configuration API
Manage proxy and policy settings
McAfee (Trellix) Queries API
Execute ePO queries and retrieve results
McAfee (Trellix) Real-Time Search API
Real-time data collection from endpoints
McAfee (Trellix) Rule Sets API
Manage web security rule sets
McAfee (Trellix) Software API
Manage software repositories and packages
McAfee (Trellix) System Groups API
Manage the ePO System Tree groups
McAfee (Trellix) Systems API
Manage endpoints and systems registered in ePO
McAfee (Trellix) Tasks API
Manage client tasks and server tasks
McAfee (Trellix) Threat Events API
Retrieve threat event data from managed endpoints
McAfee (Trellix) Threats API
Retrieve and manage detected threats
McAfee (Trellix) Watchlists API
Manage security watchlists
Scroll within the panel for all 26 ·
Open Collections 29
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 COLLECTIONMcAfee ePO Alarms API
OPEN COLLECTIONMcAfee ePO Alarms Authentication API
OPEN COLLECTIONMcAfee ePO Alarms Cases API
OPEN COLLECTIONMcAfee ePO Alarms Core API
OPEN COLLECTIONMcAfee ePO Alarms Data Sources API
OPEN COLLECTIONMcAfee ePO Alarms Detections API
OPEN COLLECTIONMcAfee ePO Alarms Devices API
OPEN COLLECTIONMcAfee ePO API
OPEN COLLECTIONMcAfee ESM API
OPEN COLLECTIONMcAfee ePO Alarms Events API
OPEN COLLECTIONMcAfee ePO Alarms File Operations API
OPEN COLLECTIONMcAfee ePO Alarms Investigations API
OPEN COLLECTIONMcAfee ePO Alarms Lists API
OPEN COLLECTIONMcAfee ePO Alarms Monitoring API
OPEN COLLECTIONMcAfee MVISION API
OPEN COLLECTIONMcAfee ePO Alarms Policies API
OPEN COLLECTIONMcAfee ePO Alarms Policy Configuration API
OPEN COLLECTIONMcAfee ePO Alarms Queries API
OPEN COLLECTIONMcAfee ePO Alarms Real-Time Search API
OPEN COLLECTIONMcAfee ePO Alarms Rule Sets API
OPEN COLLECTIONMcAfee ePO Alarms Software API
OPEN COLLECTIONMcAfee ePO Alarms System Groups API
OPEN COLLECTIONMcAfee ePO Alarms Systems API
OPEN COLLECTIONMcAfee ePO Alarms Tasks API
OPEN COLLECTIONMcAfee ePO Alarms Threat Events API
OPEN COLLECTIONMcAfee ePO Alarms Threats API
OPEN COLLECTIONMcAfee ePO Alarms Watchlists API
OPEN COLLECTIONMcAfee Web Gateway API
OPEN COLLECTIONScroll within the panel for all 29 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Mcafee Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mcafee Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Mcafee Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Mcafee Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
McAfee (Trellix) API Rules
SPECTRALJSON Schema 42
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ApiCommand
JSON SCHEMAApplianceStatus
JSON SCHEMACase
JSON SCHEMAClientTask
JSON SCHEMACommandResult
JSON SCHEMADataSource
JSON SCHEMADetection
JSON SCHEMADetectionListResponse
JSON SCHEMADetectionResponse
JSON SCHEMADevice
JSON SCHEMADeviceListResponse
JSON SCHEMADeviceResponse
JSON SCHEMAMcAfee Managed Endpoint
JSON SCHEMAEsmDevice
JSON SCHEMAFilterList
JSON SCHEMAFilterListDetail
JSON SCHEMAInvestigation
JSON SCHEMAInvestigationListResponse
JSON SCHEMAInvestigationResponse
JSON SCHEMAListEntry
JSON SCHEMALoginResponse
JSON SCHEMAPaginationMeta
JSON SCHEMAPolicy
JSON SCHEMARealTimeSearchResponse
JSON SCHEMARemediationActionResponse
JSON SCHEMARule
JSON SCHEMARuleSet
JSON SCHEMARuleSetDetail
JSON SCHEMASavedQuery
JSON SCHEMAServerTask
JSON SCHEMASoftwarePackage
JSON SCHEMASystem
JSON SCHEMASystemGroup
JSON SCHEMAMcAfee Threat Event
JSON SCHEMAThreat
JSON SCHEMAThreatEvent
JSON SCHEMAThreatListResponse
JSON SCHEMAThreatResponse
JSON SCHEMATokenResponse
JSON SCHEMATrafficStatistics
JSON SCHEMATriggeredAlarm
JSON SCHEMAWatchlist
JSON SCHEMAScroll within the panel for all 42 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Mcafee Structure
JSON STRUCTURESecurity Posture 2
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 McAfee (Trellix) — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/mcafee · machine-readable index on apis.io
This is an independent, third-party profile of McAfee (Trellix), 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.