Lightbend
Lightbend, Inc. (dba Akka) is the company behind the Akka agentic systems platform. Founded as Typesafe by the creators of the Scala language and the Akka actor toolkit, the company built the JVM reactive stack — Akka actors, Akka Streams, Akka HTTP, Akka gRPC, Akka Cluster and Play Framework — before pivoting to a full-stack platform for production agentic AI and rebranding to Akka. The current product line covers the Akka SDK (agents, orchestration, memory, streaming, HTTP/gRPC/MCP endpoints), Akka Automated Operations for multi-region deployment and operations, an in-runtime governance and policy-enforcement engine aligned to the EU AI Act, and Akka Specify, a delivered spec-driven path onto the same platform. lightbend.com now redirects to akka.io; the JVM library API surface is catalogued separately in the api-evangelist akka repository.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Lightbend the way a machine reads it — 5 machine-readable artifacts, 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 — Lightbend scores 40.0/100 (thin), with a separate agent-readiness read of 25/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 Lightbend
Each block below is one kind of artifact we hold for Lightbend. 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.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
lightbend-mcp.yml
MCP SERVERSecurity Posture 4
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.
Lightbend Trust Center
SOC 2 Type II, SOC 3 (SOC 2 Type III), ISO/IEC 27001, ISO/IEC 27002, ISO/IEC 27018, ISO/IEC 22301, ISO/IEC 42001, ISO/IEC 42005, ISO/IEC 23894, ISO/IEC 24028, CSA STAR, PCI DSS,...
SECURITYResources
Every other property we hold for Lightbend — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lightbend · machine-readable index on apis.io