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
API 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

  • 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
SolutionsTrading Bots

For Solana trading-bot developers

Solana data API for trading bots

MadeOnSol sends your Solana bot deployer alerts, KOL trades and copy-trade signals on one WebSocket stream, with token-risk and wallet context over REST; your code executes.

Try it free

  • KOL trades and deployer alerts over REST, 5 minutes delayed
  • 200 calls a day, no card needed
Get a free API key

Pro

€43/month

  • Real-time feeds, 10,000 calls a day
  • Live WebSocket (2 connections): deployer alerts, KOL trades, copy-trade signals
  • Token risk scores and copy-trade rules
Start Pro

Go further with Ultra

€131/month

  • Add the Solana DEX firehose on 3 connections and early ShredPrism signals
  • 100,000 calls a day and 20 copy-trade rules
Start Ultra

Billed in euros by card. Checkout shows today's dollar estimate; your card issuer sets the exact amount. USDC or SOL at the day's rate. Cancel anytime.

Free, Pro and Ultra keys are for your own internal use, such as bots, backends and research. Showing MadeOnSol data to your own users, for example in a public terminal or dashboard, needs Business. Compare plans

KOL wallets trackedSolana + Robinhood Chain
2,465
Deployers profiledElite → cold · of 1.5M+ indexed
124K
KOL trades capturedSolana · tracked KOL wallets · kept forever
6.69M

Build trading systems with parsed DEX activity, wallet intelligence, token context and real-time delivery, without turning your application into an indexing project.

What your bot subscribes to

Channels on wss://madeonsol.com/ws/v1/stream, one token for all of them.

  • deployer:alertsFrom Pro

    New launches from tracked deployers, with tier and track record

  • kol:tradesFrom Pro

    Buys and sells by tracked KOL wallets, with market cap at the trade

  • copytrade:signalsFrom Pro

    Your copy-trade rules firing, with a suggested size

  • token:surgesFrom Pro

    Young tokens running against their launch market cap, with risk flags

The problem

Sending a swap is only one part of a trading system. Before execution, a bot must detect the right event, interpret venue-specific activity, normalize fields, enrich wallets and tokens, filter noise and retain enough context to decide whether a signal deserves action.

Show me

What your bot receives

Start on REST with a free key, then one stream token for three channels. SDKs: TypeScript and Python as madeonsol-x402 (npm 4.4.0, PyPI 2.1.0), Rust as madeonsol (crates 0.34.0). Field names are the real payload keys; values are illustrative and the frames are abridged.

  1. First call

    A free key reads the KOL feed right away, 5 minutes delayed; a paid key gets it in real time.

    First call on a free key
    GET /api/v1/kol/feed?limit=5
    Authorization: Bearer msk_...
  2. Subscribe

    The SDK fetches the stream token, reconnects with backoff and calls your handlers with each event's data.

    TypeScript · madeonsol-x402
    import { MadeOnSolREST } from "madeonsol-x402";
    
    const rest = new MadeOnSolREST({ apiKey: process.env.MADEONSOL_API_KEY! });
    const stream = rest.stream(); // fetches the stream token, reconnects with backoff
    
    stream.on("deployer:alert", (a) => console.log(a.deployer_tier, a.token_mint));
    stream.on("kol:trade", (t) => console.log(t.kol_name, t.action, t.sol_amount));
    stream.on("copytrade:signal", (s) => console.log(s.suggested_sol_amount, s.tx_signature));
    
    stream.subscribe(["deployer:alerts", "kol:trades", "copytrade:signals"]);
  3. A launch, a KOL buy, your signal

    An elite deployer launches, a tracked KOL buys, and your copy-trade rule on that KOL fires with a suggested size.

    Frames on /ws/v1/stream (abridged)
    [
      {
        "id": "deployer:alert:918273",
        "seq": 184212,
        "channel": "deployer:alerts",
        "event": "deployer:alert",
        "data": {
          "alert_id": 918273,
          "alert_type": "new_deploy",
          "deployer_wallet": "7vfC...rXs2",
          "deployer_tier": "elite",
          "token_mint": "8vdc...pump",
          "token_symbol": "NEW",
          "launchpad": "pumpfun",
          "tx_signature": "3xQm...",
          "slot": 449476601
        },
        "ts": 1790157600000
      },
      {
        "id": "kol:trade:5K7j...",
        "seq": 184219,
        "channel": "kol:trades",
        "event": "kol:trade",
        "data": {
          "kol_name": "Cented",
          "wallet_address": "CyaE...n5Lb",
          "token_mint": "8vdc...pump",
          "token_symbol": "NEW",
          "action": "buy",
          "sol_amount": 5.27,
          "tx_signature": "5K7j...",
          "slot": 449476688,
          "traded_at": "2026-09-23T10:00:35.000Z",
          "market_cap_usd_at_trade": 28430
        },
        "ts": 1790157635000
      },
      {
        "id": "copytrade:signal:77120",
        "seq": 184220,
        "channel": "copytrade:signals",
        "event": "copytrade:signal",
        "data": {
          "signal_id": 77120,
          "subscription_id": 41,
          "subscription_name": "follow cented",
          "fired_at": "2026-09-23T10:00:36.120Z",
          "source_wallet": "CyaE...n5Lb",
          "kol_name": "Cented",
          "action": "buy",
          "token_mint": "8vdc...pump",
          "token_symbol": "NEW",
          "source_sol_amount": 5.27,
          "suggested_sol_amount": 0.5,
          "tx_signature": "5K7j...",
          "traded_at": "2026-09-23T10:00:35.000Z",
          "market_cap_usd_at_trade": 28430
        },
        "ts": 1790157636120
      }
    ]

Try it

Watch the signals before you wire a bot

A free key calls the REST API right away, with live feeds 5 minutes delayed. The KOL Tracker and surge alerts show the same data in the browser.

Get a free API key Open the KOL Tracker See token surges

Signal chain

From a new deploy to a copy-trade signal

Each step names the channel or endpoint that carries it. MadeOnSol covers detection and context; the last step is yours.

  1. 01

    MadeOnSol

    New deploy

    A tracked deployer launches a token. The alert names the deployer and the launchpad.

    deployer:alertsGET /api/v1/deployer-hunter/alerts
  2. 02

    MadeOnSol

    Deployer tier

    The alert carries deployer_tier (elite, good or rising, the tracked tiers); the profile adds bonding rate and history.

    GET /api/v1/deployer-hunter/{wallet}
  3. 03

    MadeOnSol

    Token risk

    A 0-100 score with every factor listed: mint and freeze authority, liquidity, LP burn, bundled open, deployer record. From Pro.

    GET /api/v1/tokens/{mint}/risk
  4. 04

    MadeOnSol

    KOL activity

    Tracked KOL wallets buy or sell the token, with market cap at the trade.

    kol:tradesGET /api/v1/kol/feed
  5. 05

    MadeOnSol

    Copy-trade signal

    Your rule fires with a suggested size. A rule follows any wallet you list, KOL or not; here it follows one of those KOL wallets.

    copytrade:signalsPOST /api/v1/copytrade/subscriptions
  6. 06

    Your bot

    Your bot decides

    Sizing, risk limits, building, signing and sending the swap stay in your code.

For AI agents

Agent bots

The same data is available to AI agents: as tools in the MCP server, or per call over x402 with no account.

MCP packagesx402 endpoints

MCP tools

  • madeonsol_deployer_alerts
  • madeonsol_kol_feed
  • madeonsol_token_risk
  • madeonsol_copytrade_create
  • madeonsol_tokens_surges

x402, pay per call

  • GET /api/x402/deployer-hunter/alerts
  • GET /api/x402/kol/feed
  • GET /api/x402/tokens/{mint}/risk

Capabilities

How MadeOnSol fits

01

Structured market events

Consume parsed DEX activity instead of maintaining custom decoding for every supported venue.

02

Wallet context

Enrich signals with wallet, KOL and scored early-buyer wallet intelligence where relevant.

03

Filtering

Reduce downstream noise with targeted endpoints and supported server-side filters.

04

Research plus production

Combine live delivery with queryable data on one platform.

Architecture

From chain activity to your strategy

  1. 1 · Source

    Chain activity

    Transactions and program events

  2. 2 · MadeOnSol

    Data and intelligence layer

    • Parsed DEX trades
    • KOL and early-buyer wallet context
    • Token and deployer data
  3. 3 · Delivery

    • WebSocket streams/ws/v1/stream · DEX firehose
    • Webhookssigned HTTPS push
    • REST API/api/v1 request-response
  4. 4 · Yours

    Your bot's strategy and risk logic

    Keys and business logic stay server-side

  5. 5 · Users

    Your execution

Build outcomes

What teams can build

  • Event-driven trading bots
  • Wallet-following strategies
  • Token discovery strategies
  • Market monitors
  • Signal engines

Keep going

Related

Solution

Copy Trading

Rules on wallets you choose, sized signals out.

Solution

Telegram Bots

When the bot posts alerts instead of trading.

Solution

Wallet Tracking

Events from a watchlist of any addresses.

Solution

Token Risk

Risk evidence and deployer history before the bot acts.

Guide

A first trading bot, step by step

Beginner guide in code.

Guide

A sniper bot on the DEX firehose

Filtered launch trades into a bot.

FAQ

Questions bot builders ask

Which WebSocket channels does a trading bot usually subscribe to?+
Most start with deployer:alerts for launches from tracked deployers, kol:trades for tracked KOL wallets and copytrade:signals for their own copy-trade rules; token:surges adds young tokens running against their launch market cap. One stream token covers all of them, from Pro. The streaming reference lists every channel and its plan.
Does a copy-trade signal say how much to buy?+
It suggests a size. Each signal carries suggested_sol_amount, computed from your rule's sizing mode (fixed, proportional or percent_source) and the source trade's SOL amount. Your bot decides whether to trade and how much. Copy-trade rules follow any valid wallet you list; KOL status is extra context.
What happens to the stream after a disconnect?+
The SDK reconnects and asks the server to resume after the last event your handlers finished. The server replays from its in-memory buffer or rebuilds recent events from the database, and a replay_end frame says whether the recovery was complete. Recovery is bounded, not a completeness guarantee, so dedupe on each event's id.
Can this work alongside an existing RPC provider?+
Yes, and most bots will use both. Use MadeOnSol to detect and qualify events (parsed DEX trades, KOL and wallet activity, token and deployer context), and your own RPC or execution stack to build, sign and send transactions.
REST or live transport?+
Bots that react to events usually hold a WebSocket stream open and call REST for enrichment before acting. If your service cannot keep a socket open, signed webhooks deliver supported events such as KOL trades, deployer alerts and wallet tracker events over HTTPS.
Can teams prototype first?+
Yes. Create a free API key on the developer page and call the REST API right away; on the free plan, live feeds such as the KOL feed and deployer alerts are delayed by 5 minutes. You can also try the API without signing up in the live demo. When you need real-time data, webhooks or streams, compare plans on pricing.
Does MadeOnSol execute trades?+
No. Copy-trade rules and other signals tell your bot that something happened, including a suggested size for copy-trade signals. Your bot decides whether to trade, then builds, signs and sends the transaction with its own stack.

Next step

From signal to strategy: check the data, then connect your bot.

Read the measured numbers, prototype on a free key, then open the stream on a paid plan.

  1. 1 · ProofLatency benchmarks Measured detection and serving numbers.
  2. 2 · TryGet a free API key REST right away; live feeds 5 min delayed.
  3. 3 · DocsStreaming reference Channels, frames and recovery.
  4. 4 · PlanStart Pro Real-time feeds and the stream; cancel anytime.