Telemetry
Providers using this tag (84)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 8 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 17 Early or largely undocumented
Minimal 9 Almost no public developer surface
APIs with this tag (132)
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 16 Complete, well-documented, and agent-ready
Strong 20 Solid coverage with minor gaps
Developing 39 Usable, with meaningful gaps to close
Thin 30 Limited public surface area
Emerging 24 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (90)
These companies publish an API, specification or operation carrying “Telemetry” 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.
Show all 90 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 79 providers in the APIs.io catalog tagged Telemetry, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 45.8 | 24.5 | +21.3 | 79 |
| Operational Transparency | 30.8 | 13.2 | +17.6 | 79 |
| Contract Quality | 35.1 | 18.6 | +16.5 | 79 |
| Access Clarity | 39.5 | 30 | +9.5 | 79 |
| Discoverability | 66.3 | 59.1 | +7.2 | 79 |
| Contract Governance | 15.2 | 9.7 | +5.5 | 79 |
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) | 30% | 18% | +12 |
| MCP server (first-party) | 29% | 16% | +13 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 24% | 13% | +11 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 5% | 1% | +4 |
| Governance rules | 57% | 36% | +21 |
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 Google Cloud Logging 76.2
- 2 Losant 75.7
- 3 AWS Lambda 75
- 4 The Things Network / The Things Stack 74.4
- 5 Kontakt.io 72.6
- 6 Hubble Network 71.7
- 7 Honeycomb 71.6
- 8 Enphase Energy 68.6
- 9 Splunk Observability Cloud 65.8
- 10 Elastic Observability 65.1
- 1 Losant 65.4
- 2 Chronosphere 59.6
- 3 Kontakt.io 57.3
- 4 Honeycomb 56.3
- 5 Conviva 53.6
- 6 Google Cloud Logging 50.5
- 7 Epsilon3 50
- 8 Grafana Loki 49.8
- 9 AWS Lambda 46.5
- 10 llmintel-ai 45.6
Coverage caveat. 55 of 79 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.