niche · -1.4 market domain

Endpoint Security

Score 18.8 / 100 74 providers 12 APIs Search apis.io →
Variants seen in the corpus: Endpoint ProtectionEndpoint Security

Providers using this tag (74)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 4 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 20 Early or largely undocumented
Minimal 11 Almost no public developer surface
Unrated 2 Not yet scored

APIs with this tag (12)

Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →

Exemplar 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 3 Limited public surface area
Emerging 2 Early or largely undocumented

Score breakdown

Frequency
49.1
log-scaled weighted occurrences
Breadth
1.0
spread across providers
Quality lift
31.4
mean composite of providers using it
Cohesion
0.0
strength of nearest seed neighbor

Where this tag sits

74 providers carry this tag directly, and 78 counting the 1 narrower tag below — 4 more to reach.

Security broader Cybersecurity broader Endpoint Detection and Response 16 providers

Related tags

Endpoint Detection and Response 13 co-occurrences Managed Detection and Response 12 co-occurrences Cybersecurity 56 co-occurrences XDR 8 co-occurrences Threat Detection 17 co-occurrences SIEM 11 co-occurrences Email Security 9 co-occurrences Cloud Security 15 co-occurrences

Where this tag comes from

Provider tag74
Api tag12

Markets provisional

Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.

Cohort brief

Auto-generated

The 67 providers in the APIs.io catalog tagged Endpoint Security, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
67
of 74 in the catalog
Mean Kin Score
33.7
+9.6 vs catalog 24.1
Mean Agent Readiness
14.7
+0.6 vs catalog 14.1
Spread
2.5–71.4
median 30.3 · σ 18.1
How the 67 split by band
Exemplar 4Strong 8Developing 11Thin 18Emerging 20Minimal 6
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Access Clarity 41.9 30 +11.9 67
Developer Ergonomics 35.7 24.5 +11.2 67
Operational Transparency 23.1 13.2 +9.9 67
Discoverability 66.1 59.1 +7 67
Contract Quality 23.3 18.6 +4.7 67
Contract Governance 14.2 9.7 +4.5 67

A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 19% 18% +1
MCP server (first-party) 19% 16% +3
Agent Skills 0% 0% 0
OAuth scopes 12% 13% -1
Security 97% 99% -2
Arazzo workflows 1% 1% 0
Governance rules 36% 36% 0

mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.

Top by Kin Score
  1. 1 Malwarebytes 71.4
  2. 2 Microsoft Defender 67.9
  3. 3 CrowdStrike 67.2
  4. 4 dope.security 67.1
  5. 5 Iru 65.2
  6. 6 Fleet 64
  7. 7 Armor 63.5
  8. 8 Huntress 63.5
  9. 9 JAMF 60.5
  10. 10 OpenText Cybersecurity 60
Top by Agent Readiness
  1. 1 Huntress 56.5
  2. 2 Coro 44.6
  3. 3 OpenText Cybersecurity 38.5
  4. 4 Iru 37.2
  5. 5 Armor 36.5
  6. 6 CrowdStrike 35.1
  7. 7 Adlumin 35
  8. 8 Deep Instinct 30.2
  9. 9 Malwarebytes 29.7
  10. 10 dope.security 28.9
All 74 members of this roster resolve to a provider in the catalog; 67 carry a score (91%). The figures above describe the scored members only.
Coverage caveat. 59 of 67 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.

Work with this as data

Every tag 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 tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • 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 tag
curl "https://apis.io/api/v1/tags/endpoint-security"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

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.

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