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 or to a single immutable action — decryptable only by code you’ve authorized.
Design patterns
The two structural patterns production apps on Chipotle are built from. Both work with no PKP and no trusted backend.Derived Actions
One audited template plus a stamped-in constant yields a new immutable action, with its own TEE-held key, per user, secret, or tenant.
Signed Data in Untrusted Storage
Have an action sign the records you store and verify them at runtime. Your database can fail or roll back, but it can never forge a permission.
Concepts
How the runtime works and how trust is established.Chain Secured
Your keys’ authority lives on-chain; an attested TEE enforces it by reading the chain.
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
API mode vs. ChainSecured mode — 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.
Self-Hosting
Open-source repos, deployment ownership, and the tradeoffs of operating your own Lit stack.
Reference
Lit Actions SDK
Functions available inside an action: signing, encryption, HTTP, response.
OpenAPI / Swagger
Full REST API schema — generate clients in any language.