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.4---56# Superior Trade Lighter78Use this skill for Lighter market discovery, Nautilus backtests and deployments,9managed-wallet checks, and supported typed executions through Unified API.1011Read [`../../references/unified-runtime.md`](../../references/unified-runtime.md)12before making any request. The OpenAPI contract, not older venue workflows,13defines which Lighter operations are available.1415**Base URL:** `https://unified-api-zag4gzx6gq-an.a.run.app`16**Auth:** `x-api-key: $SUPERIOR_TRADE_API_KEY`17**Venue config:** `{ "venue": "lighter", "instrument_id": "<SYMBOL>.LIGHTER" }`1819## Unified API only2021Read [`../../references/unified-runtime.md`](../../references/unified-runtime.md)22before onboarding, backtesting, deployment, or execution. Use `GET /context/venues`23and `GET /runtime/frameworks` first, then the Unified runtime endpoints. If the24contract does not expose the required Lighter operation, report it as25unavailable.2627## Robinhood Chain Variant2829Use 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.3031## Safety Rules3233- Never ask for private keys, seed phrases, API private keys, passwords, or wallet credentials.34- Never log, echo, store, or display secrets. The only credential an agent should use is `SUPERIOR_TRADE_API_KEY`.35- Never move funds or start live trading without explicit user confirmation.36- Never submit a Lighter order without explicit user confirmation of market, side, size, order type, and risk.37- Treat any contract-supported Lighter deposit or withdrawal as a real fund-moving action.38- Do not retry an ambiguous execution or withdrawal automatically. Read its durable status and report the persisted state.39- Do not claim managed-wallet funds are available on Lighter unless Unified API returns the required readiness and balance evidence.40- Do not claim Lighter readiness or balance without querying the API.41- If onboarding, CCTP funding, delayed withdrawal, or signed proxy submission is42 absent from `GET /openapi.json`, report it as unavailable.4344## Account readiness4546Read the managed wallet with `GET /wallet` and venue support with47`GET /context/venues`. Do not infer a Lighter-specific account state machine48from generic wallet history. If Unified API does not return the readiness data49needed for a live deployment, report the deployment as unavailable rather than50reusing an older onboarding flow.51## Reference files5253Load on demand.5455| Read | When |56| --- | --- |57| `references/api.md` | You need Unified routing for market context, wallet readiness, backtests, deployments, or supported typed executions. |58| `references/deployment.md` | You are creating, starting, stopping or monitoring a Lighter Nautilus deployment. |596061## Related Skills6263- Use `superior-trade-auth` first when the user needs an API key.64- Use `trade-thesis` before deploying a new live strategy idea.65- Use `hyperliquid` for Hyperliquid workflows. Lighter deployments use the same Unified runtime lifecycle with the Nautilus framework.