Epsagon
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.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
Epsagon is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Epsagon scores 8.7/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
Resources
Every other property we hold for Epsagon — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Epsagon is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/epsagon · machine-readable index on apis.io