OpenTelemetry

Vendor-neutral open-source observability framework for cloud-native software, providing a collection of tools, APIs, and SDKs for instrumenting, generating, collecting, and exporting telemetry data including metrics, logs, and traces.

OpenTelemetry publishes 6 API contracts indexed on the APIs.io network, including Logs API, Metrics API, Traces API, and 3 more. Tagged areas include Cloud-Native, Logging, Metrics, Monitoring, and Observability.

The OpenTelemetry catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

OpenTelemetry’s developer surface includes documentation, getting-started guide, engineering blog, Stack Overflow tag, changelog, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.4/100 thin ▬ flat Agent 27/100 agent aware Front door AI 3/6 light self hosted · Apache-2.0 Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

AccessFreemium

1 published contract

Cloud-Native Logging Metrics Monitoring Observability Open Source Tracing

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

SaaS Platform Operations Management

BC-4220

LogsMetricsTraces

POST /v1/logs POST /v1/metrics POST /v1/traces

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 38.4/100 · thin

Contract Quality 9.4 / 16

Developer Ergonomics 5.6 / 13

Access Clarity 1.0 / 13

Operational Transparency 3.3 / 8

Contract Governance 1.1 / 8

Discoverability 4.2 / 7

Regulatory Posture 0.9 / 15

Open Source Surface 6.5 / 10

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/opentelemetry: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

OpenTelemetry Protocol (OTLP) gRPC API

The OTLP gRPC API defines Protocol Buffers service definitions for exporting traces, metrics, and logs over gRPC. It is the primary transport for OpenTelemetry data between SDK ...

OpenTelemetry Collector API

The OpenTelemetry Collector is a vendor-agnostic proxy for receiving, processing, and exporting telemetry data. It exposes HTTP and gRPC endpoints for receiving OTLP data and pr...

OpenTelemetry SDK API

The OpenTelemetry SDK API specifies language-level interfaces for instrumentation, including the Tracer, Meter, and Logger APIs used by application code to create spans, record ...

OpenTelemetry Logs API

The Logs API from OpenTelemetry — 1 operation(s) for logs.

OpenTelemetry Metrics API

The Metrics API from OpenTelemetry — 1 operation(s) for metrics.

OpenTelemetry Traces API

The Traces API from OpenTelemetry — 1 operation(s) for traces.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

OpenTelemetry Protocol (OTLP) HTTP Logs API

OPEN COLLECTION

OpenTelemetry Protocol (OTLP) HTTP Metrics API

OPEN COLLECTION

OpenTelemetry Protocol (OTLP) HTTP Traces API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Opentelemetry Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Opentelemetry Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Opentelemetry Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

OpenTelemetry Protocol (OTLP) Telemetry Events

The OpenTelemetry Protocol (OTLP) defines the event-driven telemetry export pipeline through which instrumented applications and OpenTelemetry Collectors push batches of traces,...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

OpenTelemetry — asyncapi rules

8 rules · 7 warnings 1 info

SPECTRAL

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Opentelemetry Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LlmsText

LlmsText

Build 4

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Operate 7

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

Community

Slack

StackOverflow

ChangeLog

Scroll for all 7

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: opentelemetry
name: OpenTelemetry
description: Vendor-neutral open-source observability framework for cloud-native software, providing a collection of tools,
  APIs, and SDKs for instrumenting, generating, collecting, and exporting telemetry data including metrics, logs, and traces.
type: Index
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/opentelemetry.png
tags:
- Cloud-Native
- Logging
- Metrics
- Monitoring
- Observability
- Open Source
- Tracing
tags_raw:
- Cloud Native
- Logging
- Metrics
- Monitoring
- Observability
- Open Source
- Tracing
- Open-Source
created: '2025-01-01'
modified: '2026-04-28'
url: https://raw.githubusercontent.com/api-evangelist/opentelemetry/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: opentelemetry:opentelemetry-protocol-otlp-grpc-api
  name: OpenTelemetry Protocol (OTLP) gRPC API
  description: The OTLP gRPC API defines Protocol Buffers service definitions for exporting traces, metrics, and logs over
    gRPC. It is the primary transport for OpenTelemetry data between SDK instrumentation, the OpenTelemetry Collector, and
    observability backends, offering bidirectional streaming and efficient binary encoding.
  humanURL: https://opentelemetry.io/docs/specs/otlp/#otlpgrpc
  tags:
  - gRPC
  - Logging
  - Metrics
  - Observability
  - Tracing
  properties:
  - type: Documentation
    url: https://opentelemetry.io/docs/specs/otlp/#otlpgrpc
  - type: Reference
    url: https://opentelemetry.io/docs/specs/otlp/#otlpgrpc-response
  - type: GitHubRepository
    url: https://github.com/open-telemetry/opentelemetry-proto
- aid: opentelemetry:opentelemetry-collector-api
  name: OpenTelemetry Collector API
  description: The OpenTelemetry Collector is a vendor-agnostic proxy for receiving, processing, and exporting telemetry data.
    It exposes HTTP and gRPC endpoints for receiving OTLP data and provides a configuration API for managing pipelines, receivers,
    processors, and exporters at runtime via the zPages diagnostic extension and config file hot-reloading.
  humanURL: https://opentelemetry.io/docs/collector/
  tags:
  - Collectors
  - Configuration
  - Observability
  - Pipelines
  tags_raw:
  - Collector
  - Configuration
  - Observability
  - Pipeline
  properties:
  - type: Documentation
    url: https://opentelemetry.io/docs/collector/
  - type: Reference
    url: https://opentelemetry.io/docs/collector/configuration/
  - type: GitHubRepository
    url: https://github.com/open-telemetry/opentelemetry-collector
- aid: opentelemetry:opentelemetry-sdk-api
  name: OpenTelemetry SDK API
  description: The OpenTelemetry SDK API specifies language-level interfaces for instrumentation, including the Tracer, Meter,
    and Logger APIs used by application code to create spans, record metrics, and emit log records. Implementations are available
    for all major programming languages including Java, Python, Go, JavaScript, .NET, Ruby, and others.
  humanURL: https://opentelemetry.io/docs/specs/otel/
  tags:
  - Instrumentation
  - Logging
  - Metrics
  - SDK
  - Tracing
  properties:
  - type: Documentation
    url: https://opentelemetry.io/docs/specs/otel/
  - type: Reference
    url: https://opentelemetry.io/docs/specs/otel/trace/api/
  - type: Client Libraries
    url: https://opentelemetry.io/docs/languages/
  - type: GitHubRepository
    url: https://github.com/open-telemetry/opentelemetry-specification
- aid: opentelemetry:opentelemetry-logs-api
  name: OpenTelemetry Logs API
  description: The Logs API from OpenTelemetry — 1 operation(s) for logs.
  humanURL: https://opentelemetry.io/docs/specs/otlp/
  tags:
  - Logs
  properties:
  - type: OpenAPI
    url: openapi/opentelemetry-logs-api-openapi.yml
  - type: Documentation
    url: https://opentelemetry.io/docs/specs/otlp/
  - type: AsyncAPI
    url: asyncapi/opentelemetry-otlp-asyncapi.yml
  - type: JSONSchema
    url: json-schema.json
  - type: JSONLD
    url: context.jsonld
  - type: Reference
    url: https://opentelemetry.io/docs/specs/otlp/#otlphttp
  - type: GettingStarted
    url: https://opentelemetry.io/docs/collector/
  - type: Client Libraries
    url: https://opentelemetry.io/docs/languages/
- aid: opentelemetry:opentelemetry-metrics-api
  name: OpenTelemetry Metrics API
  description: The Metrics API from OpenTelemetry — 1 operation(s) for metrics.
  humanURL: https://opentelemetry.io/docs/specs/otlp/
  tags:
  - Metrics
  properties:
  - type: OpenAPI
    url: openapi/opentelemetry-metrics-api-openapi.yml
  - type: Documentation
    url: https://opentelemetry.io/docs/specs/otlp/
  - type: AsyncAPI
    url: asyncapi/opentelemetry-otlp-asyncapi.yml
  - type: JSONSchema
    url: json-schema.json
  - type: JSONLD
    url: context.jsonld
  - type: Reference
    url: https://opentelemetry.io/docs/specs/otlp/#otlphttp
  - type: GettingStarted
    url: https://opentelemetry.io/docs/collector/
  - type: Client Libraries
    url: https://opentelemetry.io/docs/languages/
- aid: opentelemetry:opentelemetry-traces-api
  name: OpenTelemetry Traces API
  description: The Traces API from OpenTelemetry — 1 operation(s) for traces.
  humanURL: https://opentelemetry.io/docs/specs/otlp/
  tags:
  - Traces
  properties:
  - type: OpenAPI
    url: openapi/opentelemetry-traces-api-openapi.yml
  - type: Documentation
    url: https://opentelemetry.io/docs/specs/otlp/
  - type: AsyncAPI
    url: asyncapi/opentelemetry-otlp-asyncapi.yml
  - type: JSONSchema
    url: json-schema.json
  - type: JSONLD
    url: context.jsonld
  - type: Reference
    url: https://opentelemetry.io/docs/specs/otlp/#otlphttp
  - type: GettingStarted
    url: https://opentelemetry.io/docs/collector/
  - type: Client Libraries
    url: https://opentelemetry.io/docs/languages/
common:
- type: Plans
  url: plans/opentelemetry-plans-pricing.yml
- type: RateLimits
  url: rate-limits/opentelemetry-rate-limits.yml
- type: FinOps
  url: finops/opentelemetry-finops.yml
- type: CapabilityMap
  url: capabilities/opentelemetry-capability-edges.yml
  name: OpenTelemetry Business Capability Map
- type: IssueTracker
  url: https://github.com/open-telemetry/opentelemetry-proto/issues
- type: Releases
  url: https://github.com/open-telemetry/opentelemetry-proto/releases
- type: CodeOfConduct
  url: https://github.com/open-telemetry/.github/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/open-telemetry/opentelemetry-proto/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/open-telemetry/opentelemetry-proto/blob/main/LICENSE
- type: DomainSecurity
  url: security/opentelemetry-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/opentelemetry
- url: https://opentelemetry.io/
  name: OpenTelemetry
  type: Website
  description: Official OpenTelemetry project website.
- url: https://opentelemetry.io/docs/
  name: Documentation
  type: Documentation
  description: Official OpenTelemetry documentation hub.
- url: https://opentelemetry.io/docs/getting-started/
  name: Getting Started
  type: GettingStarted
  description: Guides for getting started with OpenTelemetry instrumentation.
- url: https://github.com/open-telemetry
  name: GitHub Organization
  type: GitHubOrganization
  description: OpenTelemetry GitHub organization containing all project repositories.
- url: https://github.com/open-telemetry/opentelemetry-specification
  name: OpenTelemetry Specification
  type: GitHubRepository
  description: The OpenTelemetry specification defining APIs, SDKs, and data models.
- url: https://opentelemetry.io/docs/languages/
  name: SDKs
  type: SDKs
  description: OpenTelemetry SDK implementations for all supported programming languages.
- url: https://opentelemetry.io/blog/
  name: Blog
  type: Blog
  description: OpenTelemetry project blog with announcements and technical articles.
- url: https://opentelemetry.io/community/
  name: Community
  type: Community
  description: Community resources including CNCF Slack, SIG meetings, and contribution guides.
- url: https://cloud-native.slack.com/archives/CJFCJHG4Q
  name: Slack
  type: Slack
  description: OpenTelemetry community Slack channel in the CNCF Slack workspace.
- url: https://stackoverflow.com/questions/tagged/open-telemetry
  name: Stack Overflow
  type: StackOverflow
  description: OpenTelemetry-tagged questions and answers on Stack Overflow.
- url: https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md
  name: Change Log
  type: ChangeLog
  description: Changelog for the OpenTelemetry specification.
- url: https://github.com/open-telemetry/opentelemetry-collector/security/policy
  name: Security
  type: Security
  description: Security disclosure policy for the OpenTelemetry project.
- type: Integrations
  url: https://opentelemetry.io/ecosystem/integrations/
- type: LlmsText
  url: https://opentelemetry.io/llms.txt
integrations:
- name: English EN
- name: Registry
- name: Adopters
- name: Distributions
- name: Vendors
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/opentelemetry"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/opentelemetry/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/opentelemetry/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.