Solana analytics API: query history, then stay live

Show me

Query history, then stay live

One dashboard panel: launch outcomes by deployer tier over 30 days. REST gives the starting state, the stream moves it, a timer reconciles. Keys are the route's and the emitters' own; values are illustrative and bodies abridged.

1. 1 · Load the state

   alert-stats counts every deploy and bond alert in the window and breaks them out by tier (elite, good, rising). It works on a Free key.

   GET /api/v1/deployer-hunter/alert-stats (abridged)

   // GET /api/v1/deployer-hunter/alert-stats?period=30d
   {
     "bond_rate": { "total_deploys": 3120, "total_bonded": 702, "rate": 22.5 },
     "tiers": {
       "elite":  { "deploys": 210, "bonded": 131, "bond_rate": 62.4, "avg_multiplier": 12.4, "total_with_mc": 81 },
       "good":   { "deploys": 288, "bonded": 122, "bond_rate": 42.4, "avg_multiplier": 9.8, "total_with_mc": 86 },
       "rising": { "deploys": 371, "bonded": 109, "bond_rate": 29.4, "avg_multiplier": 6.1, "total_with_mc": 79 }
     },
     "period": "30d",
     "sampled_rows": 452,
     "truncated": false
   }

2. 2 · Apply the events

   Subscribe to deployer:alerts (from Pro). Each deployer:alert adds a deploy, each deployer:bond a bond, under the tier in the frame.

   TypeScript · madeonsol-x402

   import { MadeOnSolREST } from "madeonsol-x402";
   
   const rest = new MadeOnSolREST({ apiKey: process.env.MADEONSOL_API_KEY! });
   
   // 1 · Initial state: the last 30 days of launch outcomes by deployer tier
   let state = await rest.deployerAlertStats({ period: "30d" });
   
   // 2 · Stay live: one frame moves one counter
   const stream = rest.stream();
   stream.on("deployer:alert", (a) => {
     state.bond_rate.total_deploys += 1;
     const t = state.tiers[a.deployer_tier];
     if (t) t.deploys += 1;
   });
   stream.on("deployer:bond", (b) => {
     state.bond_rate.total_bonded += 1;
     const t = state.tiers[b.deployer_tier];
     if (t) t.bonded += 1;
   });
   stream.subscribe({ subId: "launch-outcomes", channels: ["deployer:alerts"] });
   
   // 3 · Reconcile: the window slides and deployers change tier
   setInterval(async () => {
     state = await rest.deployerAlertStats({ period: "30d" });
   }, 5 * 60_000);

3. 3 · What arrives

   A launch by an elite deployer, then its bond 18 minutes later. Both frames carry a stable id, so a replayed frame never counts twice.

   Frames on /ws/v1/stream (abridged)

   [
     {
       "channel": "deployer:alerts",
       "sub_id": "launch-outcomes",
       "event": "deployer:alert",
       "id": "deployer:alert:918273",
       "seq": 402551,
       "data": {
         "alert_id": 918273,
         "alert_type": "new_deploy",
         "deployer_wallet": "7vfC...rXs2",
         "deployer_tier": "elite",
         "token_mint": "8vdc...pump",
         "token_symbol": "NEW",
         "launchpad": "pumpfun",
         "bonding_rate": 0.64,
         "total_bonded": 41,
         "total_deployed": 64,
         "market_cap_at_alert": 6200,
         "tx_signature": "3xQm...",
         "slot": 449476601
       },
       "ts": 1790330400000
     },
     {
       "channel": "deployer:alerts",
       "sub_id": "launch-outcomes",
       "event": "deployer:bond",
       "id": "deployer:bond:8vdc...pump",
       "seq": 402987,
       "data": {
         "deployer_wallet": "7vfC...rXs2",
         "deployer_tier": "elite",
         "token_mint": "8vdc...pump",
         "token_symbol": "NEW",
         "launchpad": "pumpfun",
         "time_to_bond_minutes": 18,
         "instant_bond": false,
         "bonding_rate": 0.65,
         "total_bonded": 42,
         "total_deployed": 64,
         "market_cap_at_alert": 69400
       },
       "ts": 1790331480000
     }
   ]

Keeping them in agreement

When the live numbers and the REST numbers differ

Events only add. The REST aggregate is recomputed from storage on each read. These are the cases where the two part ways, and the fix for each.

Streaming reference for resume, replay_end and gap reporting.

Beyond raw RPC

Questions an RPC response cannot answer on its own

An RPC node returns transactions and account state. The questions an analytics product asks need attribution, prices you can reproduce, coverage you can read and a record of what was known when.

Choosing the surface

Which part of the API each product need maps to

Plans come from each route's own gate and the channel table. For every swap on a venue, see DEX Data; this page covers what sits around it. Endpoint catalog

Historical data

How far back each dataset goes

MadeOnSol keeps the datasets it models, each with a stated start and window. It is not an index of every Solana program: trade history covers launchpad tokens, and anything outside the table below needs another source. Data dictionary · How the archive is verified

Bulk exports · Live correctness checks · Label definitions

Architecture

From stored history and live events to your dashboard

1. 1 · Source

   Chain activity

   Transactions and program events

3. 2 · MadeOnSol

   Data and intelligence layer

   • Launchpad trade history and candles
   • Deployer, KOL and wallet intelligence
   • Point-in-time snapshots and manifests

5. 3 · Delivery

   • REST API/api/v1 history and aggregates
   • WebSocket streamsdeployer:alerts · kol:trades · token:candles
   • Webhooksdeployer:alert · deployer:bond · kol:trade

7. 4 · Yours

   Your state store and reconcile job

   Keys and business logic stay server-side

9. 5 · Users

   Your dashboard or research tool

• Launch outcome dashboards by deployer tier
• Token research pages with trade history and candles
• KOL and alpha-wallet leaderboards
• Backtests on point-in-time reputation
• Warehouse loads from monthly Parquet files
• Reports that cite the dataset state behind each number

Showing MadeOnSol data to your own users requires a Business plan. See pricing