Lightrun
Lightrun is a developer-native observability and live-debugging platform. Language agents embedded in a running JVM, Python, Node.js or .NET process accept dynamic actions — logs, snapshots, counters, tic-toc timings and custom metrics — placed on a file and line while the application keeps serving traffic, so engineers can inspect production behavior without redeploying, restarting or attaching a traditional debugger. The platform is driven from JetBrains, VS Code and Visual Studio plugins, a Java CLI, a bearer-authenticated Public REST API, and a published MCP server that gives AI coding assistants live runtime context. Around that core it adds agent-pool RBAC, PII redaction, SSO and SCIM provisioning, and a Dynamic SBOM surface that reports which third-party packages are actually reachable at runtime.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Lightrun the way a machine reads it — 27 machine-readable artifacts across 20 APIs, 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 — Lightrun scores 58.1/100 (developing), with a separate agent-readiness read of 75/100 (agent native). 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.
How we profile Lightrun
Each block below is one kind of artifact we hold for Lightrun. 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 20
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.
Lightrun Actions API
Actions API.
Lightrun Agent Pools API
Agent Pools API.
Lightrun Agents API
Agents API.
Lightrun Custom sources API
Custom sources API.
Lightrun Debug Cases API
Debug Cases API.
Lightrun Debug Runbook methods API
The Debug Runbook methods API from Lightrun — 1 operation(s) for debug runbook methods.
Lightrun Debug Runbooks API
Debug Runbooks API.
Lightrun Debug Runbooks Configuration API
Debug Runbooks Configuration API.
Lightrun Dynamic SBOM API
Dynamic SBOM API.
Lightrun Identity Management (IdM) configuration API
Identity Management (IdM) configuration API
Lightrun Just-In-Time Access API
Just-In-Time Access API.
Lightrun License API
Company License API.
Lightrun Lightrun feature flags status API
Lightrun feature flags status API.
Lightrun Loaded packages API
Loaded packages API.
Lightrun SMTP connectivity configuration API
SMTP connectivity configuration API
Lightrun System access API key API
System access API key management API.
Lightrun Tags API
Tags API.
Lightrun User Groups API
User Groups API.
Lightrun Users API
Users API.
Lightrun Watched packages API
Watched packages API.
Scroll within the panel for all 20 ·
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.
lightrun-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Lightrun Webhooks
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Lightrun — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lightrun · machine-readable index on apis.io