# Epsagon

**Canonical:** https://apis.io/providers/epsagon/  
**APIs profiled:** 0

Epsagon was an observability and application performance monitoring (APM) company, founded in 2017, that provided automated distributed tracing for serverless and containerized applications — AWS Lambda, Node.js, Python, Go, .NET, Ruby, and Java — correlating traces, metrics, and logs to help teams identify and fix problems fast without manual instrumentation. Epsagon was acquired by Cisco in 2021 and folded into Cisco's observability portfolio, after which the product was sunset. The epsagon.com developer surface (docs, dashboard, and API subdomains) no longer resolves. Its surviving public footprint is the github.com/epsagon organization and the first-party instrumentation SDKs still hosted on npm, PyPI, RubyGems, Go modules, NuGet, and Maven Central. This profile captures that remaining, verifiable footprint.

## Kin Score — 7.5 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 7.5).

| Facet | Score |
|---|---|
| Discoverability | 57.4 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 2.6 |
| Developer Ergonomics | 7.1 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Tags

Company, Observability, Monitoring, Application Performance Monitoring, Distributed Tracing, Serverless, Containers, OpenTelemetry

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/epsagon/). Scores are computed from the provider's own public artifacts under a published rubric.