Telemetry
Providers using this tag (75)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 8 Almost no public developer surface
APIs with this tag (111)
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 11 Complete, well-documented, and agent-ready
Strong 16 Solid coverage with minor gaps
Developing 42 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 23 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (73)
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 73 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 74 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.2 | 23.2 | +22 | 74 |
| Operational Transparency | 33.9 | 13.7 | +20.2 | 74 |
| Contract Quality | 34.7 | 17.6 | +17.1 | 74 |
| Access Clarity | 37.9 | 26.5 | +11.4 | 74 |
| Discoverability | 64.5 | 58.1 | +6.4 | 74 |
| Contract Governance | 11.4 | 6.3 | +5.1 | 74 |
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% | 14% | +17 |
| MCP server (first-party) | 28% | 12% | +16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 23% | 11% | +12 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 23% | 14% | +9 |
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 Losant 83.1
- 2 The Things Network / The Things Stack 79.2
- 3 Hubble Network 70.4
- 4 AWS Lambda 69.8
- 5 Google Cloud Logging 67.4
- 6 Honeycomb 66.5
- 7 Grafana Loki 66.1
- 8 Splunk Observability Cloud 65.7
- 9 Enphase Energy 63.8
- 10 Chronosphere 62.4
- 1 Losant 62.3
- 2 Chronosphere 56.6
- 3 Conviva 53.6
- 4 Kontakt.io 50.5
- 5 Epsilon3 50
- 6 Grafana Loki 49.8
- 7 Google Cloud Logging 46.8
- 8 Honeycomb 45.4
- 9 Cronitor 42.8
- 10 Starlink 38.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.