Zero to Lit Action
- Create an account via the Dashboard, note down your API key. Account creation takes ~15 seconds — it registers your account on-chain (Base).
- Add funds — click Add Funds in the Dashboard (minimum $5.00) and pay with a credit card, crypto (ETH, USDC, SOL and more), or LITKEY. Running Lit Actions and metered/write management operations consume credits, while read-only management calls (for example listing resources or checking your balance) are free. Unfunded metered calls return
402 Payment Required— see Errors. - Add a usage API key — set its permissions by clicking All Options
- Run a Lit Action
- From the Dashboard
- Programmatically via cURL/JavaScript
- or build your own SDK from the OpenAPI spec
Using the Dashboard
The Dashboard is a web management GUI for Lit. It supports light/dark themes and provides simple tools for managing accounts, keys, wallets, and actions. Recommended workflow:- Request a new account (or log in)
- Add funds via credit card
- Request usage API keys
- Request new PKPs (wallets)
- Register IPFS CIDs (actions)
- Create groups
- Run lit-actions
Using the API directly
The same workflows are available via the REST API under/core/v1/. All authenticated endpoints expect the API key in a header (X-Api-Key or Authorization: Bearer).
Workflow:
- New account or verify account (login)
- Add funds — card, crypto, or the billing API
- Add usage API key
- Create wallet (PKP)
- Add group and register IPFS action
- Add PKP to group (optional)
- Run lit-action
Daily Usage
The Dashboard is just your human-friendly configuration tool. Once your account and keys are set up, you can call the lit-action endpoint with your usage key every time you, your dApp, or a cron job needs to execute an action:- Call the API with your usage key, action code (or IPFS CID), and any parameters you need.
Next steps
- Lit Actions Overview — what they are and how they run
- Examples — signing, encryption, HTTP fetching, contract calls
- Architecture — the TEE / on-chain / IPFS layers
- Chain Secured — why your keys’ authority lives on-chain, and how an attested TEE enforces it
- OpenAPI Spec / Swagger UI