Superior Trade Lighter
Use this skill for Lighter market discovery, Nautilus backtests and deployments,
managed-wallet checks, and supported typed executions through Unified API.
Read ../../references/unified-runtime.md
before making any request. The OpenAPI contract, not older venue workflows,
defines which Lighter operations are available.
Base URL: https://unified-api-zag4gzx6gq-an.a.run.app
Auth: x-api-key: $SUPERIOR_TRADE_API_KEY
Venue config: { "venue": "lighter", "instrument_id": "<SYMBOL>.LIGHTER" }
Unified API only
Read ../../references/unified-runtime.md
before onboarding, backtesting, deployment, or execution. Use GET /context/venues
and GET /runtime/frameworks first, then the Unified runtime endpoints. If the
contract does not expose the required Lighter operation, report it as
unavailable.
Robinhood Chain Variant
Use the separate lighter-robinhood skill and venue name for Robinhood Chain Lighter. Do not treat lighter-robinhood as an alias for this default lighter profile; it uses a different venue profile, chain id, deposit asset, and instrument suffix.
Safety Rules
- Never ask for private keys, seed phrases, API private keys, passwords, or wallet credentials.
- Never log, echo, store, or display secrets. The only credential an agent should use is
SUPERIOR_TRADE_API_KEY.
- Never move funds or start live trading without explicit user confirmation.
- Never submit a Lighter order without explicit user confirmation of market, side, size, order type, and risk.
- Treat any contract-supported Lighter deposit or withdrawal as a real fund-moving action.
- Do not retry an ambiguous execution or withdrawal automatically. Read its durable status and report the persisted state.
- Do not claim managed-wallet funds are available on Lighter unless Unified API returns the required readiness and balance evidence.
- Do not claim Lighter readiness or balance without querying the API.
- If onboarding, CCTP funding, delayed withdrawal, or signed proxy submission is
absent from
GET /openapi.json, report it as unavailable.
Account readiness
Read the managed wallet with GET /wallet and venue support with
GET /context/venues. Do not infer a Lighter-specific account state machine
from generic wallet history. If Unified API does not return the readiness data
needed for a live deployment, report the deployment as unavailable rather than
reusing an older onboarding flow.
Reference files
Load on demand.
| Read |
When |
references/api.md |
You need Unified routing for market context, wallet readiness, backtests, deployments, or supported typed executions. |
references/deployment.md |
You are creating, starting, stopping or monitoring a Lighter Nautilus deployment. |
Related Skills
- Use
superior-trade-auth first when the user needs an API key.
- Use
trade-thesis before deploying a new live strategy idea.
- Use
hyperliquid for Hyperliquid workflows. Lighter deployments use the same Unified runtime lifecycle with the Nautilus framework.
1---2name: lighter3description: "Use when researching, backtesting, deploying, or running a supported one-time Lighter action through the Superior Trade Unified API."4metadata:5 version: 1.0.26 updated: 2026-07-227 homepage: https://account.superior.trade8 source: https://github.com/Superior-Trade9 primaryEnv: SUPERIOR_TRADE_API_KEY10 auth:11 type: api_key12 env: SUPERIOR_TRADE_API_KEY13 header: x-api-key14 scope: "Read the user's Unified wallet and Lighter market context, and manage contract-supported Nautilus backtests and deployments. One-time actions, venue-specific onboarding, deposits, and withdrawals are available only when the Unified OpenAPI contract explicitly exposes them. Cannot export private keys or access other users' data."15 env:16 - name: SUPERIOR_TRADE_API_KEY17 description: "Superior Trade API key (x-api-key header). Obtained at https://account.superior.trade. Used for Unified wallet reads, market context, backtests, and contract-supported Lighter deployments."18 required: true19 type: api_key20 externalEndpoints:21 - url: https://unified-api-zag4gzx6gq-an.a.run.app22 purpose: "Unified Lighter market context, wallet reads, backtests, and deployments"23---2425# Superior Trade Lighter2627Use this skill for Lighter market discovery, Nautilus backtests and deployments,28managed-wallet checks, and supported typed executions through Unified API.2930Read [`../../references/unified-runtime.md`](../../references/unified-runtime.md)31before making any request. The OpenAPI contract, not older venue workflows,32defines which Lighter operations are available.3334**Base URL:** `https://unified-api-zag4gzx6gq-an.a.run.app`35**Auth:** `x-api-key: $SUPERIOR_TRADE_API_KEY`36**Venue config:** `{ "venue": "lighter", "instrument_id": "<SYMBOL>.LIGHTER" }`3738## Unified API only3940Read [`../../references/unified-runtime.md`](../../references/unified-runtime.md)41before onboarding, backtesting, deployment, or execution. Use `GET /context/venues`42and `GET /runtime/frameworks` first, then the Unified runtime endpoints. If the43contract does not expose the required Lighter operation, report it as44unavailable.4546## Robinhood Chain Variant4748Use the separate `lighter-robinhood` skill and venue name for Robinhood Chain Lighter. Do not treat `lighter-robinhood` as an alias for this default `lighter` profile; it uses a different venue profile, chain id, deposit asset, and instrument suffix.4950## Safety Rules5152- Never ask for private keys, seed phrases, API private keys, passwords, or wallet credentials.53- Never log, echo, store, or display secrets. The only credential an agent should use is `SUPERIOR_TRADE_API_KEY`.54- Never move funds or start live trading without explicit user confirmation.55- Never submit a Lighter order without explicit user confirmation of market, side, size, order type, and risk.56- Treat any contract-supported Lighter deposit or withdrawal as a real fund-moving action.57- Do not retry an ambiguous execution or withdrawal automatically. Read its durable status and report the persisted state.58- Do not claim managed-wallet funds are available on Lighter unless Unified API returns the required readiness and balance evidence.59- Do not claim Lighter readiness or balance without querying the API.60- If onboarding, CCTP funding, delayed withdrawal, or signed proxy submission is61 absent from `GET /openapi.json`, report it as unavailable.6263## Account readiness6465Read the managed wallet with `GET /wallet` and venue support with66`GET /context/venues`. Do not infer a Lighter-specific account state machine67from generic wallet history. If Unified API does not return the readiness data68needed for a live deployment, report the deployment as unavailable rather than69reusing an older onboarding flow.70## Reference files7172Load on demand.7374| Read | When |75| --- | --- |76| `references/api.md` | You need Unified routing for market context, wallet readiness, backtests, deployments, or supported typed executions. |77| `references/deployment.md` | You are creating, starting, stopping or monitoring a Lighter Nautilus deployment. |787980## Related Skills8182- Use `superior-trade-auth` first when the user needs an API key.83- Use `trade-thesis` before deploying a new live strategy idea.84- Use `hyperliquid` for Hyperliquid workflows. Lighter deployments use the same Unified runtime lifecycle with the Nautilus framework.
Superior-Trade