The Business tier (€400/mo, self-serve) licenses you to display MadeOnSol data inside your own product — 500k calls/day, 10 WS + 5 firehose connections. Enterprise above adds white-label & redistribution rights and custom endpoints.
If you're building a trading terminal, bot, dashboard, or AI agent on Solana, the memecoin-intelligence layer — KOL flow, deployer reputation, coordination signals, a MEV-stripped DEX firehose — is the part that's painful to build in-house. This is the builder's guide to embedding it instead: what the data is, how to access it (REST, WebSocket, webhooks, MCP, SDKs), and when to white-label it under your own brand.
Thousands of tokens launch on Solana every day, and almost all of them are noise. The signal isn't in the token — it's in who deployed it. A wallet that has bonded 8 of its last 10 launches operates differently from a serial rugger on launch number 400, and that history is knowable the second a new deploy hits the chain.
This tutorial gives your Discord server that awareness. You'll run the open-source deployer-alert-discord-bot starter (MIT, ~130 lines, zero npm dependencies): when a tracked deployer with a proven record launches a new token — or one of their tokens bonds — your channel gets an embed within seconds to minutes, with the track record attached.
It's powered by the MadeOnSol Deployer Hunter, which scores deployer wallets from their full on-chain launch history — runners, rugs, bond rates — across pump.fun and LaunchLab (bonk).
Data only, DYOR: a good deployer track record is a signal, not a guarantee. MadeOnSol never executes trades, and neither does this bot.
What lands in your channel
🚀 New deploy: $TICKER · 🟠 Bonk
Tracked deployer deployed a new token. 8/10 lifetime bonds.
MC at alert $45.0k · Deployer tier elite · Track record 8/10 bonded (80%)
Purple embeds are new deploys, green are bonds, and LaunchLab launches carry the 🟠 badge. Every embed links to the deployer's full profile page so your members can inspect the history before touching anything.
Step 1 — Two tokens, then run
git clone https://github.com/madeonsol/deployer-alert-discord-bot
cd deployer-alert-discord-bot
# 1. Free API key (200 req/day, no payment): https://madeonsol.com/pricing
export MADEONSOL_API_KEY=msk_your_key_here
# 2. Discord webhook: Server Settings → Integrations → Webhooks → New
export DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...
node index.mjs
No Discord server handy? DRY_RUN=1 node index.mjs prints the embeds to your terminal instead of posting.
Two details the starter already handles that you'd otherwise learn the hard way: state persists in state.json so restarts don't re-post old alerts, and the first boot posts at most three recent alerts instead of flooding a fresh channel with the whole backlog.
Step 2 — Understand the polling budget
| Key | Poll interval | Daily budget |
|---|
| Free (BASIC) | 480 s | fits comfortably in 200 req/day |
| PRO / ULTRA | 60 s — or real-time via the deployer:alerts WebSocket channel | 10k / 100k req/day |
The bot reads your tier from GET /me and picks the interval itself. On the free tier an alert arrives up to ~8 minutes after the deploy — enough for "watch this deployer" awareness. PRO cuts that to a minute, and the WebSocket channel makes it effectively instant, which matters if your server acts on new deploys rather than just discussing them.
Step 3 — Tune what's worth pinging
The alert payload carries the full deployer object, so filtering is one if statement:
- Elite only:
alert.deployers.tier === "elite" — the strictest cut, a handful of alerts a day instead of a stream.
- Launchpad split:
alert.launchpad === "launchlab" for a bonk-only channel, or the inverse for pump.fun purists.
- Route by tier: send elite deploys to
#alpha with an @here, everything else to a quiet #deploy-log. Two webhooks, three lines of code.
Step 4 — Score the token, not just the deployer
A proven deployer can still ship a bad launch. The natural upgrade is scoring the token itself at alert time: POST /tokens/batch/risk (PRO) returns a 0–100 rug score with named factors — mint authority, liquidity, LP burn, bundled-launch detection — in one ~200ms call. That's the same scoring engine behind the rug-check Telegram bot tutorial, and combining the two turns "tracked deployer launched something" into "tracked deployer launched something and it passes ten safety checks."
For the full picture of why deployer history predicts outcomes — and what the bond-rate distribution actually looks like — see why most pump.fun tokens fail in the first hour.
Beyond the starter
If this bot becomes a product — a paid alert service, a terminal feature, an agent input — the same data is available as REST, WebSocket, and webhooks with delivery receipts. The builder's guide to embedding Solana memecoin intelligence maps those integration paths, and the KOL copy-trade starter shows the same free-key-first pattern applied to smart-money flow.
Once polling isn't fast enough, the webhook-driven Discord bot walkthrough and its Telegram counterpart show how to get the same deployer alerts pushed in real time with HMAC-signed delivery instead of a poll loop.
Full endpoint reference: madeonsol.com/api-docs. Free key and plans: madeonsol.com/pricing.
