MadeOnSolMade on Sol

Data APIs

Solana Data APIRobinhood Chain API

Intelligence

Telegram AlertsKOL TrackerWallet ScannerToken LookupDeployer Hunter
Trading BotsTrading TerminalsWallet TrackingToken Scanners
View all solutions
Optimization guidesAPI DocsWebSocket StreamingMCP & SDKsx402 for AI AgentsAgent Intelligence Gateway
Discover ToolsCompare ToolsSubmit a ToolAdvertiseBlog
Pricing
Get real-time feedsSign in
MadeOnSolMade on Sol

Solana and Robinhood Chain intelligence — KOL wallet tracking, deployer intelligence, all-DEX trade streams, and a developer API. Discover, compare, and build.

Product

  • Solana Data API
  • Solana Wallet Checker
  • Robinhood Chain Wallet Checker
  • Robinhood Chain API
  • Robinhood Chain x402
  • MCP Servers & SDKs
  • x402 for AI Agents
  • Agent Intelligence Gateway
  • Pricing
  • Enterprise / For Businesses

Solutions

  • Trading Bots
  • Wallet Tracking
  • Copy Trading
  • Token Scanners
  • Trading Terminals
  • DEX Data
  • Smart Money
  • Token Risk
  • AI Agents
  • ShredPrism Stream
  • View all solutions

Developers

  • Optimization guides
  • API Docs
  • WebSocket Streaming
  • Changelog
  • API Status
  • Latency Benchmarks
  • Data Integrity
  • Data Dictionary
  • Methodology

Resources

  • All Tools
  • Compare Tools
  • Best Trading Bots
  • Best DEXs
  • Best Wallets
  • Best Analytics
  • Best DeFi
  • Best Snipers
  • Blog
  • Blog Archive
  • Signal Scorecard
  • Tool Uptime
  • Community
  • Submit a Tool
  • Advertise

Company

  • About
  • Contact
  • Security
  • Privacy
  • Terms
  • DPA
  • Disclaimer

© 2026 MadeOnSol

MadeOnSol — eenmanszaak, Hulshout, Belgium · KBO/BTW BE 1039.535.538 (art. 56bis, no VAT charged)

Runs on our own dedicated EU servers — self-hosted data stack, own Robinhood Chain node · security

Powered by:constant·k — Private Solana RPC Services
Browse all guides
Optimization guidesValidate a KOL feed before increasing request volumeProcess webhook retries without duplicate effectsRecover a WebSocket feed after a disconnectReduce REST polling in a trading terminalMerge live candles with historical OHLCVCache KOL rankings while streaming tradesBudget REST calls and WebSocket slotsTake a MadeOnSol API integration from prototype to productionBuild reliable MadeOnSol WebSocket recoveryReduce MadeOnSol API calls with safe backend cachingScale a MadeOnSol terminal to multiple viewersInterpret token amounts, timestamps and data quality correctlyBuild reliable trading alerts with MadeOnSol dataMeasure MadeOnSol usage and choose the right API planKeep Solana top holder rankings in syncBuild a live Solana bundle monitorSize WebSocket bandwidth for a trading terminalCalculate locked liquidity across Solana poolsReconcile Robinhood Chain holder counts and transfersAPI reference
Optimization guidesValidate a KOL feed before increasing request volumeProcess webhook retries without duplicate effectsRecover a WebSocket feed after a disconnectReduce REST polling in a trading terminalMerge live candles with historical OHLCVCache KOL rankings while streaming tradesBudget REST calls and WebSocket slotsTake a MadeOnSol API integration from prototype to productionBuild reliable MadeOnSol WebSocket recoveryReduce MadeOnSol API calls with safe backend cachingScale a MadeOnSol terminal to multiple viewersInterpret token amounts, timestamps and data quality correctlyBuild reliable trading alerts with MadeOnSol dataMeasure MadeOnSol usage and choose the right API planKeep Solana top holder rankings in syncBuild a live Solana bundle monitorSize WebSocket bandwidth for a trading terminalCalculate locked liquidity across Solana poolsReconcile Robinhood Chain holder counts and transfersAPI reference
Optimization guidesBuild a live Solana bundle monitor

Pro and above · Compare plans and subscribe

Build a live Solana bundle monitor

Track coordinated Solana buys and exits over WebSocket, deduplicate wallet exposure and distinguish proven bundle holdings from same-slot estimates.

By MadeOnSol · Updated 2026-11-19

Integration choice

Treat a bundle event as a trigger to refresh the affected mint. Use the bundle-share response for current holdings and keep its observation time, evidence basis and scope beside the percentage.

Before you startImplementation stepsWhat does proven bundle ownership measure?Work through an overlapping-wallet exampleHandle a sell alert inside the cache intervalCode examplesCommon mistakesVerify your integrationProduction checklistQuestions

Before you start

  • Use one mint, a fixed observation window and server-side credentials.
  • Log event identity and the measurement’s as_of separately so replay is testable.

Implementation steps

  1. Set SOLANA_MINT to a traded mint. Load bundle-share with an explicit comparison window such as 24h. Keep the same window and min_wallets across requests.
  2. Watch token:bundles for the mints in view. On a new cluster or exit, mark its cached reading dirty. Coalesce refreshes by mint, window and threshold across viewers.
  3. Keep the strict lower bound and the broader same-slot figure in separate fields. Replace a successful reading atomically. Preserve null and the returned scope when balance evidence is incomplete.
  4. Deduplicate repeated event deliveries before issuing notifications. After recovery, refresh the current measurement once and keep historical exit events in their own timeline.

What does proven bundle ownership measure?

The strict percentage measures current supply held by wallets linked through the supported launch-bundle or same-transaction evidence. It is a lower bound. The broad percentage also considers same-slot buying. Independent buyers can share a busy slot, so a scanner should retain that distinction in its labels.

Map strict_bundle_pct_of_supply_now to the proven lower bound and bundled_pct_of_supply_now to the broader reading. Store bundled_pct_basis, scope and as_of with the numbers. A later response can have different evidence even when the displayed percentage stays the same.

Work through an overlapping-wallet example

Suppose the first cluster contains A and B, and a later one contains B and C. At one observation their balances are 30, 20 and 10 out of 1,000 units. For that illustrative cohort the distinct-wallet share is 6%. Adding the cluster totals produces 8% by counting B twice. Historical buy amounts answer a different question from current balances.

Handle a sell alert inside the cache interval

An exit milestone describes sales by tracked wallets. A balance may also leave through a transfer. Keep the latest measured share and its as_of on screen while refreshing. The standard share read is cached for 30 seconds, so repeated reads in that interval can legitimately return the same observation.

Code examples

Subscribe on an authenticated Node.js socket

const token = process.env.SOLANA_MINT;
if (!token) throw new Error("Set SOLANA_MINT first");
socket.send(JSON.stringify({
  type: "subscribe",
  sub_id: "solana-live-bundle-monitor",
  channels: ["token:bundles"],
  filters: { mints: [token] }
}));

Read current holdings for the 24-hour window

curl -H "Authorization: Bearer $MADEONSOL_API_KEY" "https://madeonsol.com/api/v1/tokens/$SOLANA_MINT/bundle-share?window=24h&min_wallets=3"

Common mistakes and fixes

Common integration mistakes and recommended fixes
MistakeRecommended fix
A transfer is presented as a sale.Require an exit event for a sale milestone. Use share measurements for current exposure.
A restricted reading looks like full coverage.Carry scope, evidence basis and missing values through storage and rendering.

Verify your integration

Feed the same event twice, then a second cluster containing a previously seen wallet. Expect one alert for the duplicate and one shared refresh per cache interval. Simulate a null share and a launch-cohort-only response and check their labels.

Production checklist

  • Duplicate events produce one alert.
  • The query window is displayed.
  • Strict and broad percentages have separate labels.

Frequently asked questions

Can I add launch and later cluster percentages?

Wallets can belong to both. Use the deduplicated share response for the selected population.

Does a null percentage mean every wallet exited?

No. A null measurement can reflect missing balance evidence. A measured zero and an unavailable value require different handling.

Continue building

  • Recover a WebSocket feed after a disconnect
  • Reduce MadeOnSol API calls with safe backend caching
  • Interpret token amounts, timestamps and data quality correctly

Match your plan to your workload

Compare capacity, channel access and display rights before launching.

Compare plans and subscribe
Read this guide as Markdown
Streaming referenceLive terminal demoStream subscription builder