How a non-coder builds Meteora SDK tools with AI, and what I built with it.
If you can say it in one sentence, the AI can build version 1 tonight. It is for you. No login, no landing page, no users.

















DLMM Alert. Tells you when a position falls out of range, before it is too late.
dlmmalert.app
DLMM Checker. Screens a token before you LP it. RugCheck, Jupiter and Meteora data in one place.
dlmmchecker.vercel.app
Pool and copier tools, and Meridian, an autonomous LP executor.
meteoraidn.comDiscord token alert and notification bots. The pings a lot of you already run on.

TrackLP. Wallet PnL, leaderboards, alerts, copy trading, an extension, a replay, an agent. Next slide.
tracklp.comNobody was hired to build these. Each one started as a problem the app did not solve.
Wallet positions into a sheet
Apr 2025Finds the best moments in Meteora streams, renders the clips with captions
Jan 2026Helius webhooks into Telegram
Jan 2026tracklp.com. PnL, leaderboards, wallet pages
Jan to Feb 2026Webhook, job, on-chain. SOL only, hard cap
Feb 2026Quick Position. Open a DLMM position on meteora.ag in one click
2026Paste signatures, get a video of how a wallet traded a token. Built on the clipper's render engine
Aug 2026Claude Code on a VPS reviewing the book twice a day and posting to Telegram
Aug 2026Make an empty folder. Open Claude Code in it. That is the only setup.
Paste the prompt on the right. It installs the SDK, reads it, asks you for what it needs, writes the script and runs it.
When it asks, give it a Helius RPC URL and a wallet. Use a public wallet from the TrackLP leaderboard, not your own.
Open the same wallet on meteora.ag. Check the numbers match. If they do not, tell it what is wrong and let it fix it.
I have never installed a package by hand. The agent does it.
One sentence. What the tool should show you, for which wallet or pool. Add one thing at a time.
Installs, reads the SDK, writes the code, runs it, prints the result. If it errors, it fixes it. You watch.
Open the same wallet on meteora.ag or Solscan. Do the bins match? The amounts? The fees? If not, that is your next sentence.
"Now add fees per hour." "Now only show positions out of range." Each one is a two-minute loop.
Name the wallet, the fields and the shape of the output.
This is the first thing my own test hit tonight. The fix was one sentence: "That errored, fix it and run it again." It wrapped the code in a function and moved on.
Paste the error back, say what you expected, let it try again.
If it has an RPC and the SDK, it can read anything on Solana. Most problems are not knowledge problems. They are one more loop.
It writes old v1 calls against the v2 SDK and sounds certain. Make it read the installed package first. Every session.
A transaction can confirm and move nothing. If your tool signs anything, it reads the result back on chain and stops if it does not match. On 18 Aug one of my copies was rejected 6 times for a slippage setting it never needed.
Token-2022 and pump.fun tokens can report raw amounts. Take decimals from the balance changes, or you get 9-figure positions that do not exist.
LP Agent allows 5 requests a minute. Two of your own scripts will block each other. One queue, one key.
The AI never gets a key that holds real funds. Burner wallet, small size, check it works, then scale.
I keep a LEARNINGS file. 30 entries. Each one is something the AI did wrong with full confidence, and I only caught it by checking the chain.
Hand the AI the SDK, then make it prove every number on a real wallet before you believe it.
Start read-only. Start tonight. The kit, the prompt and the follow-ups are at tracklp.com/ai-starter-guide