niche · 0.3 capabilitymarket actiondomain

Log Management

Score 19.3 / 100 26 providers +4 via APIs 9 APIs Search apis.io →

Providers using this tag (26)

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

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

APIs with this tag (9)

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 3 Complete, well-documented, and agent-ready
Developing 1 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Emerging 3 Early or largely undocumented

Companies reaching this through an API (4)

These companies publish an API, specification or operation carrying “Log Management” 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.

Datadog Oracle Software Development Lifecycle VMware

Score breakdown

Frequency
42.1
log-scaled weighted occurrences
Breadth
0.7
spread across providers
Quality lift
37.6
mean composite of providers using it
Cohesion
7.4
strength of nearest seed neighbor

Related tags

SIEM 13 co-occurrences Security Operations 5 co-occurrences Threat Detection 9 co-occurrences Logging 6 co-occurrences Observability 21 co-occurrences Monitoring 14 co-occurrences Query 6 co-occurrences DevOps 9 co-occurrences

Where this tag comes from

Provider tag26
Api tag9

Cohort brief

Auto-generated

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

Providers
25
of 26 in the catalog
Mean Kin Score
31.8
+8.9 vs catalog 22.9
Mean Agent Readiness
16.3
+4.4 vs catalog 11.9
Spread
0–74.6
median 35.2 · σ 20.3
How the 25 split by band
Exemplar 2Strong 2Developing 4Thin 7Emerging 6Minimal 4
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Operational Transparency 28 13.7 +14.3 25
Developer Ergonomics 34.8 23.2 +11.6 25
Access Clarity 36.1 26.5 +9.6 25
Contract Quality 22.1 17.6 +4.5 25
Discoverability 62.1 58.1 +4 25
Contract Governance 9.3 6.3 +3 25

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) 40% 14% +26
MCP server (first-party) 32% 12% +20
Agent Skills 0% 0% 0
OAuth scopes 20% 11% +9
Security 100% 98% +2
Arazzo workflows 0% 2% -2
Governance rules 20% 14% +6

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 74.6
  2. 2 Google Cloud Logging 67.4
  3. 3 SolarWinds 62.5
  4. 4 Panther 54.6
  5. 5 Mezmo 52
  6. 6 Axiom 44.7
  7. 7 Google Cloud Chronicle 43
  8. 8 Quickwit 42.1
  9. 9 Motadata 38.6
  10. 10 Devo 36.3
Top by Agent Readiness
  1. 1 Axiom 48.9
  2. 2 Google Cloud Logging 46.8
  3. 3 Securonix 41.2
  4. 4 LogicMonitor 33.8
  5. 5 Panther 30.8
  6. 6 Middleware 29.9
  7. 7 Mezmo 28.4
  8. 8 Google Cloud Chronicle 24.8
  9. 9 Axiom 24.8
  10. 10 SolarWinds 24.6
All 26 members of this roster resolve to a provider in the catalog; 25 carry a score (96%). The figures above describe the scored members only.
Coverage caveat. 18 of 25 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 5 October 2026, across 29093 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/log-management"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/log-management"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/log-management/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

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.