Pulse

Site and docs: https://nirholas.github.io/pulse/

npx pulse-trenches            # collector, API and dashboard on :8787
npx -y -p pulse-trenches pulse-mcp   # MCP server for agents (set PULSE_URL)

Personal market intelligence for the Solana and Robinhood Chain trenches. Pulse watches every launch, runner and death, scores wallets, labels KOLs, classifies tokens by tech versus meme, writes a daily newsletter to Telegram, and archives everything in Postgres so the history can later train a trading bot.

What it records

Export any table as JSON from /api/export/<table>.

Run it

Requires Node 24 or newer.

npm install
cp .env.example .env       # optional, everything has a default
npm run build              # builds the dashboard into dist/web
npm start                  # collector + firehose + API + dashboard on http://localhost:8787

With no DATABASE_URL, Pulse stores data in an embedded PGlite database at data/pglite. For TimescaleDB:

npm run db:up              # Postgres on host port 5544
echo 'DATABASE_URL=postgres://pulse:pulse@localhost:5544/pulse' >> .env

Other commands:

Permanent archive in git

Set ARCHIVE_REPO to a repo you own (gh repo create <you>/pulse-data --private) and ARCHIVE_TOKEN to a token with contents:write. Each finished UTC day is then exported to that repo as gzip JSONL, a runner digest (runners/YYYY-MM-DD.json) and, with ANTHROPIC_API_KEY, an AI brief on what ran and what technology is being built. The repo is the history: pulse archive --restore rebuilds a database from it, and an agent can read it directly or call the pulse_runners MCP tool. See docs/archive.md.

Telegram newsletter

Create a bot with @BotFather, add it to your channel as an admin, and set TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID (for example @my_channel). The issue is generated once a day at REPORT_HOUR in REPORT_TIMEZONE, stored first, then sent. Set ANTHROPIC_API_KEY to add a short written overview that is constrained to the day's data.

Data sources

All keyless: Jupiter token lists, DexScreener, pump.fun, GeckoTerminal, Solana RPC logs for the pump.fun and PumpSwap programs, Robinhood Chain RPC factory logs, and public KOL wallet labels. The public Solana WebSocket drops connections often; Pulse reconnects, but a dedicated SOLANA_WS_URLS endpoint keeps the firehose steady.

Layout

src/collector   firehose, scheduler, Robinhood walker, persistence
src/sources     one client per data provider
src/intel       classification, lifecycle status, wallet scoring
src/report      newsletter data, rendering, Telegram, narrative
src/server      Hono API and static dashboard hosting
src/db          migrations and the Postgres/PGlite client
web             Vite dashboard (board, command, markets, solana, tokens, token detail, launches, wallets, newsletter)

Token names, symbols and descriptions are untrusted on-chain input. The dashboard escapes every interpolation and Pulse never acts on them.

MIT licensed.

Support the project

If pulse saves you time, star it on GitHub. Stars are how other developers and AI agents find the repositories worth trusting, and they cost you one click.

Know someone who would use it? Post on X · Share on Bluesky · Share on LinkedIn · Submit to Hacker News · Share on Reddit

Built for AI agents too

Coding agents and LLM tooling can read this repo directly: AGENTS.md, llms.txt, llms-full.txt. Point an agent at https://github.com/nirholas/pulse and it has the context it needs.

More from the same author

• All repositories by nirholas: the full catalog, grouped by topic
• three.ws: the platform for 3D AI agents with Solana wallets, a skill marketplace and x402 payments
• Questions or ideas: open an issue or start a discussion

Contributors

Star history