OpenTelemetry
Providers using this tag (47)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 11 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (15)
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 2 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 4 Early or largely undocumented
Companies reaching this through an API (6)
These companies publish an API, specification or operation carrying “OpenTelemetry” 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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 46 providers in the APIs.io catalog tagged OpenTelemetry, 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 | 56.7 | 23.2 | +33.5 | 46 |
| Operational Transparency | 43.8 | 13.7 | +30.1 | 46 |
| Access Clarity | 50.2 | 26.5 | +23.7 | 46 |
| Contract Quality | 39.1 | 17.6 | +21.5 | 46 |
| Contract Governance | 17.7 | 6.3 | +11.4 | 46 |
| Discoverability | 68.2 | 58.1 | +10.1 | 46 |
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) | 59% | 14% | +45 |
| MCP server (first-party) | 54% | 12% | +42 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 37% | 11% | +26 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 7% | 2% | +5 |
| Governance rules | 30% | 14% | +16 |
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 Datadog APM 81.9
- 2 ThousandEyes 75
- 3 LogicMonitor 74.6
- 4 Better Stack 68.5
- 5 Google Cloud Logging 67.4
- 6 Moesif 66.9
- 7 Grafana Loki 66.1
- 8 Splunk Observability Cloud 65.7
- 9 Embrace 65
- 10 Logz.io 65
- 1 APIContext 60.1
- 2 Dash0 57.7
- 3 Chronosphere 56.6
- 4 ThousandEyes 56.3
- 5 Datadog APM 56
- 6 Better Stack 55.6
- 7 Embrace 52.2
- 8 Superlog 50.7
- 9 Groundcover 50
- 10 Grafana Loki 49.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.