Providers using this tag (36)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 3 Almost no public developer surface
APIs with this tag (16)
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 5 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Emerging 5 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 36 providers in the APIs.io catalog tagged APM, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 42.6 | 17.5 | +25.1 | 36 |
| Developer Ergonomics | 38.9 | 17.9 | +21 | 36 |
| Access Clarity | 41.8 | 22.3 | +19.5 | 36 |
| Operational Transparency | 30.3 | 11.3 | +19 | 36 |
| Contract Governance | 15 | 6.4 | +8.6 | 36 |
| Discoverability | 68.2 | 60.4 | +7.8 | 36 |
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.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 31% | 16% | +15 |
| MCP server (first-party) | 8% | 7% | +1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 19% | 9% | +10 |
| Security | 92% | 88% | +4 |
| Arazzo workflows | 17% | 2% | +15 |
| Governance rules | 56% | 13% | +43 |
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.
- 1 Centers for Medicare and Medicaid Services 85.2
- 2 Dynatrace 71.8
- 3 New Relic 68.8
- 4 Highlight (highlight.io) 66.7
- 5 Sentry 61.3
- 6 Dash0 60.6
- 7 Splunk Observability Cloud 60.6
- 8 VividCortex 57.7
- 9 Datadog 57.1
- 10 Flipdish 54
- 1 Dash0 54.7
- 2 Sentry 44.6
- 3 Centers for Medicare and Medicaid Services 39.7
- 4 Datadog 38.3
- 5 Splunk Observability Cloud 36.7
- 6 Flipdish 35.2
- 7 SigNoz 35.1
- 8 Splunk 34
- 9 Dynatrace 32.4
- 10 New Relic 31.7
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/apm"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/apm"
curl "https://apis.io/api/v1/cohorts/tag/apm/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.