Librato
Librato was a hosted metrics, monitoring and analytics service for operational data — time-series measurements, tagged metrics, dashboards ("spaces"), charts, annotations, alerts and notification services — delivered as a developer-first SaaS with a JSON REST API at metrics-api.librato.com/v1. Backed by Cowboy Ventures among others, the San Francisco company was acquired by SolarWinds in 2015 for a reported $40 million, and its metrics platform was folded into SolarWinds AppOptics — released in November 2017 — which has itself since reached end of life. The librato.com domain and every product subdomain (metrics., status., www.) now 301-redirect to the SolarWinds AppOptics end-of-life notice, the metrics-api.librato.com API host no longer resolves in DNS, and the github.com/librato organization was archived on 2024-01-02. This profile is retained as a historical record of a well-regarded developer API: the API reference source, the first-party Ruby, Python, Java and Node client libraries and the collection agents remain publicly archived and are catalogued here. The successor product is SolarWinds Observability SaaS.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Librato the way a machine reads it — 3 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
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 — Librato scores 19.7/100 (emerging), with a separate agent-readiness read of 17/100 (agent aware). 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
How we profile Librato
Each block below is one kind of artifact we hold for Librato. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Librato Metrics API
RETIRED. JSON REST API for submitting and retrieving time-series measurements and for managing metrics, metric attributes, spaces, charts, dashboards, instruments, annotations, ...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Librato — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/librato · machine-readable index on apis.io