Use these docs with AI
Give Claude, Cursor, Devin, ChatGPT or any AI agent access to the Lighter docs via llms.txt and Markdown pages.
These docs are designed to be read by AI assistants and coding agents as well as people.
llms.txt
https://docs.lighter.xyz/llms.txt lists every guide and API endpoint with a one-line summary and a link to its Markdown version. Point your agent at it to discover pages.
Markdown pages
Add .md to any page URL to get clean Markdown:
https://docs.lighter.xyz/developers/getting-started/quickstart-typescript.md
https://docs.lighter.xyz/api/transactions.mdFor a section's landing page, use readme.md instead: https://docs.lighter.xyz/developers/readme.md, /api/readme.md, /evm/readme.md, /programs/readme.md.
Tell your agent how to build on Lighter
Drop the Agent instructions into your repo as AGENTS.md / CLAUDE.md / .cursor/rules/lighter.mdc so your coding agent follows Lighter's rules (decimals, nonces, key safety) by default.
Devin
Commit the Agent instructions as
AGENTS.mdin the root of the repo Devin works on. Devin reads it automatically at the start of every session.Optionally, add a skill for Lighter work at
.agents/skills/lighter/SKILL.md, so Devin looks up the docs before writing Lighter code:
Letting an AI agent trade
If you're building an agent that trades on a user's behalf:
Give it a dedicated API key on a dedicated sub-account funded with only what it may risk.
Use a read-only token for any agent that only needs to look. See Read-only Authentication.
Never give an agent the user's Ethereum private key. API keys can't send funds to other owners.
Keep a human confirmation step for withdrawals, transfers and large orders.
For Cursor, save these rules in .cursor/rules/lighter.mdc and prepend:
Last updated
Was this helpful?