Telemetry
Telemetrytelemetry
Providers using this tag (74)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 20 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 14 Early or largely undocumented
Minimal 8 Almost no public developer surface
APIs with this tag (115)
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 5 Complete, well-documented, and agent-ready
Strong 19 Solid coverage with minor gaps
Developing 42 Usable, with meaningful gaps to close
Thin 26 Limited public surface area
Emerging 23 Early or largely undocumented
Companies reaching this through an API (80)
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 80 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 72 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.9 | 23.4 | +22.5 | 72 |
| Operational Transparency | 34.4 | 14 | +20.4 | 72 |
| Contract Quality | 36.6 | 19.8 | +16.8 | 72 |
| Access Clarity | 37.3 | 26.5 | +10.8 | 72 |
| Discoverability | 66.9 | 61.2 | +5.7 | 72 |
| Contract Governance | 11 | 6.4 | +4.6 | 72 |
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) | 26% | 10% | +16 |
| MCP server (first-party) | 29% | 13% | +16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 25% | 11% | +14 |
| Security | 100% | 97% | +3 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 19% | 14% | +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.
- 1 Honeycomb 80.6
- 2 Losant 79.5
- 3 The Things Network / The Things Stack 78.1
- 4 Enphase Energy 68.6
- 5 Hubble Network 68.5
- 6 Kontakt.io 65.3
- 7 Google Cloud Logging 64.2
- 8 Cisco Catalyst Center 63.4
- 9 Grafana Loki 62.5
- 10 ThingsBoard 62.3
- 1 Losant 62.3
- 2 Chronosphere 56.6
- 3 Conviva 53.6
- 4 Kontakt.io 51.8
- 5 Grafana Loki 49.8
- 6 Honeycomb 47.1
- 7 Google Cloud Logging 46.8
- 8 Sift Stack 39.7
- 9 Starlink 38.3
- 10 Cisco Catalyst Center 37.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.