Lightning.AI
Lightning AI is an AI development cloud from the creators of PyTorch Lightning. The platform bundles browser-based GPU Studios, batch and multi-node training jobs, autoscaled model and container deployments, ephemeral code-execution Sandboxes, teamspace data and model registries, and an OpenAI-compatible LLM gateway (Model APIs) that fronts hosted models from OpenAI, Anthropic, Google and open-weights providers behind one key and one bill. Developers reach the platform through the lightning-sdk Python package and its lightning CLI, an @lightningai/sdk TypeScript SDK for Sandboxes, and a v1 REST surface reachable with the `lightning api` escape hatch. Lightning AI also publishes an llms.txt, a docs manifest registry, and six first-party Agent Skills in SKILL.md format for coding agents.
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 Lightning.AI the way a machine reads it — 5 machine-readable artifacts across 2 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 — Lightning.AI scores 30.5/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 Lightning.AI
Each block below is one kind of artifact we hold for Lightning.AI. 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 2
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.
Lightning AI Model APIs
OpenAI-compatible LLM gateway. Call hosted models from OpenAI, Anthropic, Google and open-weights providers through a single Bearer-authenticated endpoint with one bill, using p...
Lightning AI Platform API
The v1 REST surface behind the Lightning AI platform — Studios, Jobs, multi-machine training, Deployments, Sandboxes, teamspaces, memberships, datasets and the model checkpoint ...
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lightningai Rate Limits
RATE LIMITSSecurity 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 Lightning.AI — 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 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 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lightningai · machine-readable index on apis.io