OpenTelemetry
OpenTelemetryOpentelemetry
Providers using this tag (43)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (14)
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
Developing 3 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 43 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 | 45 | 17.9 | +27.1 | 43 |
| Operational Transparency | 32.9 | 11.3 | +21.6 | 43 |
| Contract Quality | 38.8 | 17.5 | +21.3 | 43 |
| Access Clarity | 38.7 | 22.3 | +16.4 | 43 |
| Discoverability | 71.1 | 60.4 | +10.7 | 43 |
| Contract Governance | 14.8 | 6.4 | +8.4 | 43 |
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) | 40% | 16% | +24 |
| MCP server (first-party) | 30% | 7% | +23 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 9% | +7 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 9% | 2% | +7 |
| Governance rules | 37% | 13% | +24 |
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 ThousandEyes 70.2
- 2 New Relic 68.8
- 3 Highlight (highlight.io) 66.7
- 4 Logz.io 65.2
- 5 Embrace 61.1
- 6 Dash0 60.6
- 7 Splunk Observability Cloud 60.6
- 8 Honeycomb 60
- 9 Mezmo 53.7
- 10 Agnost AI 52.2
- 1 Dash0 54.7
- 2 ThousandEyes 51.1
- 3 Embrace 50.9
- 4 Superlog 50
- 5 Agnost AI 48.3
- 6 Splunk Observability Cloud 36.7
- 7 LangWatch 36.3
- 8 SigNoz 35.1
- 9 Honeycomb 34
- 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/opentelemetry"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/opentelemetry"
curl "https://apis.io/api/v1/cohorts/tag/opentelemetry/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.