telemetry.dev valid

telemetry.dev

LLM observability for AI agents and applications, built on OpenTelemetry. Trace instrumented model calls, tool steps, and retrievals. Inspect reported token usage, cost, latency, and errors. Connect through first-party TypeScript or Python SDKs, provider and framework integrations, or an existing OTLP/HTTP exporter.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:03:08.407Z. Cached copy · Source on telemetry.dev

# telemetry.dev

> LLM observability for AI agents and applications, built on OpenTelemetry. Trace instrumented model calls, tool steps, and retrievals. Inspect reported token usage, cost, latency, and errors. Connect through first-party TypeScript or Python SDKs, provider and framework integrations, or an existing OTLP/HTTP exporter.

Use this index to find machine-readable pages. Add `.md` to a public page's path for its Markdown form, such as `https://telemetry.dev/docs/integrations/openai.md` or `https://telemetry.dev/docs/quickstart.md`. For the documentation homepage, use [docs/index.md](https://telemetry.dev/docs/index.md). Product pages outside `/docs` also answer `Accept: text/markdown`; documentation pages under `/docs` return HTML for that header, so use the `.md` URL there.

## How agents should use telemetry.dev

- For research, follow the `.md` links below. Each markdown page links onward with `.md` URLs.
- For setup instructions, SDK APIs, and the ingest contract, start from the [documentation index](https://telemetry.dev/docs/llms.txt). The whole documentation set is in [docs/llms-full.txt](https://telemetry.dev/docs/llms-full.txt).
- For all public product pages in one request, fetch [llms-full.txt](https://telemetry.dev/llms-full.txt).
- For the ingest API, read the [OTLP ingest reference](https://telemetry.dev/docs/reference/otlp.md), the [API key guide](https://telemetry.dev/docs/platform/api-keys.md), and the [OpenAPI description](https://telemetry.dev/openapi.json) before sending data.
- Paths under `/o/`, `/login`, `/signup`, and `/dashboard` are the interactive app and need a browser session.

## Product capabilities

- **AI trace inspection:** View an instrumented request or agent run as a span hierarchy. Inspect model inputs and outputs, tool arguments and results, retrievals, errors, timing, and per-span attributes when the source instrumentation emits them.
- **Search and filtering:** Search traces or individual spans and filter by status, environment, framework, user, or conversation.
- **Usage dashboards:** Track requests, cost, p95 latency, input and output tokens, error rate, and OpenTelemetry metric series over 7-, 30-, or 90-day windows. Break down usage by model, provider, environment, user, or framework.
- **Token and cost accounting:** Record input, output, cache-read, cache-write, and reasoning tokens when reported by the provider or instrumentation. telemetry.dev calculates cost at ingest from reported token usage and its model-pricing catalog. Cache-read and cache-write tokens use separate rates when available. Reasoning tokens are not charged separately. An explicit span cost takes precedence. Without matching model pricing or token usage, computed cost is unavailable.
- **Streaming measurements:** Record end-to-end latency and time to first token when the integration exposes streaming timing.
- **Correlated signals:** Store OTLP traces, logs, and metrics in the same project. Logs can carry trace and span
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=telemetry.dev · GET /v1/domain/telemetry.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for telemetry.dev:
1. POST https://agentwebmap.com/v1/sites/telemetry.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://telemetry.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/telemetry.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/telemetry.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.