niche · -1.3 market domain

Network Monitoring

Score 17.0 / 100 25 providers +2 via APIs 4 APIs Search apis.io →

Providers using this tag (25)

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

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

APIs with this tag (4)

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
Developing 3 Usable, with meaningful gaps to close

Companies reaching this through an API (2)

These companies publish an API, specification or operation carrying “Network Monitoring” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.

Azure Networking Services VMware

Score breakdown

Frequency
37.3
log-scaled weighted occurrences
Breadth
0.3
spread across providers
Quality lift
35.2
mean composite of providers using it
Cohesion
3.4
strength of nearest seed neighbor

Where this tag sits

Monitoring broader

Related tags

Synthetic Monitoring 5 co-occurrences AIOps 6 co-occurrences Observability 14 co-occurrences Monitoring 12 co-occurrences Networking 7 co-occurrences Infrastructure 5 co-occurrences Company 15 co-occurrences

Where this tag comes from

Provider tag25
Api tag4

Cohort brief

Auto-generated

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

Providers
21
of 25 in the catalog
Mean Kin Score
37.4
+13.3 vs catalog 24.1
Mean Agent Readiness
17.3
+3.2 vs catalog 14.1
Spread
3.2–80.3
median 35.1 · σ 21.9
How the 21 split by band
Exemplar 3Strong 2Developing 4Thin 5Emerging 4Minimal 3
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 41.7 24.5 +17.2 21
Operational Transparency 29.7 13.2 +16.5 21
Access Clarity 45.2 30 +15.2 21
Contract Quality 29.1 18.6 +10.5 21
Discoverability 65.5 59.1 +6.4 21
Contract Governance 12.3 9.7 +2.6 21

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) 23% 18% +5
MCP server (first-party) 23% 16% +7
Agent Skills 0% 0% 0
OAuth scopes 14% 13% +1
Security 95% 99% -4
Arazzo workflows 0% 1% -1
Governance rules 41% 36% +5

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 LogicMonitor 80.3
  2. 2 Progress Software 78.6
  3. 3 SolarWinds 68.5
  4. 4 Kentik 62.6
  5. 5 Catchpoint 59.4
  6. 6 Celona 48
  7. 7 Busymate DevTools 47.4
  8. 8 Site24x7 40
  9. 9 AppNeta 39.9
  10. 10 Motadata 35.5
Top by Agent Readiness
  1. 1 Progress Software 47
  2. 2 Busymate DevTools 40.5
  3. 3 LogicMonitor 33.7
  4. 4 netmon-com 28.7
  5. 5 Kentik 28.2
  6. 6 AppNeta 28.1
  7. 7 SolarWinds 27
  8. 8 Catchpoint 26.9
  9. 9 Celona 23.6
  10. 10 Netbeez 19.8
All 25 members of this roster resolve to a provider in the catalog; 21 carry a score (84%). The figures above describe the scored members only.
Coverage caveat. 15 of 21 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/network-monitoring"
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.