Lit is a programmable runtime that reads data from any source, runs your JavaScript inside a chain-secured TEE, and signs on any chain or API. Keys never leave the enclave, and the code that’s allowed to use them is governed on-chain. You get the speed and expressiveness of a single trusted runtime, with the auditability of a smart contract.Documentation Index
Fetch the complete documentation index at: https://developer.litprotocol.com/llms.txt
Use this file to discover all available pages before exploring further.
Start here: Quick Start
Create an account, fund it, and run your first Lit Action in a few minutes — via the Dashboard or the REST API.
Build
The fastest paths to a running integration.Dashboard
Web GUI for accounts, API keys, wallets (PKPs), IPFS actions, and groups.
REST API
Drive the same workflows from cURL, the lightweight JS SDK, or your own client built from the OpenAPI spec.
Lit Actions
JavaScript that runs inside the network’s TEE — read, decide, sign, in one file.
Use cases
Patterns you can build on one programmable runtime.Cross-chain actions
Read state on one chain, sign on another — bridges, mirrors, and replays without a multisig in the middle.
Custom oracles
Aggregate any HTTP or RPC feed inside the TEE, sign the result with a PKP, deliver it anywhere a signature is trusted.
Conditional signing
Sign only when on- or off-chain conditions hold — sanctions screens, price thresholds, KYC checks, dispute windows.
Encrypted secrets
Encrypt API keys, credentials, or user data under a PKP — decryptable only by an action you’ve authorized on-chain.
Concepts
How the runtime works and how trust is established.Architecture
The three layers: chain-secured TEE, on-chain permissions, and IPFS-hosted actions.
Auth Model
How API keys, scopes, and account ownership combine to authorize requests.
Groups
Bind Programmable Key Pairs to permitted action CIDs and usage keys.
Verification
Attest that the enclave is running the code it claims to be running.
Operate
Account ownership, billing, and key management.Account Modes
SaaS vs. self-sovereign — picking an ownership model and migrating between them.
API Keys
Account keys vs. usage keys, and how to scope them.
Pricing
Credit-based billing, how requests are metered, and how to add funds.
Reference
Lit Actions SDK
Functions available inside an action: signing, encryption, HTTP, response.
OpenAPI / Swagger
Full REST API schema — generate clients in any language.