Example repos
Working projects on this API to clone, run and hand to your assistant as the pattern to follow.
Every example is TypeScript, runs with npm start, reads its secrets from .env (template in .env.example), has a DRY_RUN=1 mode that builds and simulates without sending, and logs every API error code. An assistant that reads one of them produces the same shape.
| Repo | What it does | Status |
|---|---|---|
| pumpfun-launcher | Full launcher UI: wallets, metadata upload, create + up to 16 bundled buyers via lookup tables, live trades, sells, creator fees. Backend talks only to this API. | Working; in this repository under demos/pumpfun-launcher. Public GitHub repo being prepared. |
| sniper-bot | Watches subscribeNewToken, filters, buys, takes profit / stops out, persists positions. | Coming. Until then: the Build with AI sniper prompt produces it. |
| take-profit-bot | Take-profit, stop-loss and trailing rules for coins you already hold. | Coming (prompt available). |
| copy-trader | Mirrors buys and sells of watched wallets with subscribeAccountTrade. | Coming (prompt available). |
| pons-bot | Robinhood chain: launches and trades on pons through the ordered-transaction flow. | Coming (prompt available). |
| sdk | @trenchytools/sdk: typed client generated from openapi.json, retries, 429 handling, websocket helper. | In this repository under packages/sdk (0.1, not yet published). |
GitHub links land here as each repo is published. Until then, the prompts on Build with AI plus openapi.json are enough for an assistant to generate any of them.
What an example must have
- TypeScript, Node 20+,
npm start README.mdwith setup in five steps.env.examplewith every variable; no secret anywhere elseDRY_RUN=1: build + simulate, never send- One place that maps API error
code→ what the bot does next - No private key ever leaves the process; no Lightning (custodial) endpoints