Your Memecoin Volume Number Is Lying: Strip MEV at the Data Layer

Most Solana volume figures conflate organic trader flow with MEV bot wash — sandwich bots double-count every victim swap on the same pool. MadeOnSol separates them on the way in: every swap is tagged organic or mev-suspect, and the API exposes both `organic_volume_usd` and `mev_volume_pct` per window.

MadeOnSol·May 14, 2026· 7 min read

Your Memecoin Volume Number Is Lying: Strip MEV at the Data Layer

Disclosure: This article contains affiliate links. If you sign up through them, MadeOnSol may earn a commission at no extra cost to you. This never affects our rankings, ratings, or reviews.

Building a product on Solana or Robinhood Chain data?

Skip the Geyser pipeline — embed KOL flow, deployer reputation, and the all-DEX firehose over REST, WebSocket, or webhooks. The Business tier (€400/mo) is the self-serve embed license at 500k calls/day — Enterprise adds white-label & redistribution.

See Business pricing

Tools mentioned

Compare features and read reviews.

Live health scores, average ratings, and direct links on MadeOnSol.

DoubleZero

High-speed dedicated fiber network for Solana validators and infrastructure

extrnode

Decentralized Solana RPC gateway with auto-failover across a node cluster

Nodit

Enterprise Web3 data and RPC infrastructure with indexed APIs, nodes, and event streams.

Build with MadeOnSol API

KOL tracking, deployer intelligence, DEX streaming, and webhooks. Free API key — 200 requests/day.

Start free

import { MadeOnSol } from "madeonsol";

// Get a free API key at madeonsol.com/pricing
const client = new MadeOnSol({ apiKey: "msk_your_key" });

const { trades } = await client.kol.feed({ limit: 10 });
const { alerts } = await client.deployer.alerts({ limit: 5 });
const { tools } = await client.tools.search({ q: "trading" });

npm install madeonsolFull API docs

Building a product on Solana or Robinhood Chain data?

MadeOnSol isn't an RPC or another generic token API — it's Solana & Robinhood Chain memecoin intelligence that's painful to build in-house, pulled from dual-region gRPC shred streams and our own Robinhood Chain node, pushed to your app as events land.

Signals you'd otherwise build

KOL & smart-money flow from 2,000+ labeled wallets, deployer reputation, coordination clusters, linked-wallet entity resolution, and an all-DEX firehose.

Keep reading

More from the blog.

All API Guides

Guides

How to Get pump.fun Token Trades via API: the Per-Mint Trade Tape (2026)

One GET returns every buy and sell on a pump.fun token, newest first, with the executed price, the pool price at that slot, the wallet and the early-buyer rank. Cursor paging, buy/sell and wallet filters, and what the coverage block tells you before you trust the numbers.

9 minSeptember 5, 2026

Guides

How to Stream New Solana Token Launches over WebSocket: Deploys, Graduations, Surges (2026)

One socket, three channels: sniper:deploys pushes every pump.fun launch a few hundred milliseconds before the chain confirms it, token:graduations pushes every bonding-curve completion, token:surges pushes young tokens running 3×, 6× or 8× against their launch cap. Handshake, real frames, filters, and what each channel does not tell you.

Enjoyed this article?

Explore the live data.

Real-time KOL trades, Pump.fun deployer intel, and 1,200+ ranked Solana & Robinhood Chain tools — free to explore.

Open the KOL Tracker

API reference Start free Browse all articles

Explore more

Top 10 API Platforms Top 10 RPC Deployer Hunter KOL Tracker Compare Yields Solana Glossary

A worked example: pulling a clean scanner

A common scanner spec for memecoin trading is "fresh momentum with real traders." Without MEV filtering, that query reliably surfaces tokens that are 50%+ bot floor — false-positives that look pumping but have no demand under the bot layer.

import { MadeOnSol } from "madeonsol";

const client = new MadeOnSol({ apiKey: process.env.MADEONSOL_API_KEY! });

async function freshOrganicMomentum() {
  const { tokens } = await client.tokens.list({
    min_mc: 50_000,
    max_mc: 5_000_000,
    min_liq: 5000,
    active_h: 4,
    min_volume_1h_usd: 30_000,
    max_mev_share_pct: 20,
    mc_change_1h_min_pct: 30,
    sort: "last_trade_desc",
    limit: 30,
  });

  return tokens.map((t) => ({
    mint: t.mint,
    symbol: t.symbol,
    mc: t.market_cap_usd,
    mc_change_1h: t.mc_change_1h_pct,
    organic_vol_1h: t.organic_volume_1h_usd,
    mev_share: t.mev_share_pct,
    primary_dex: t.primary_dex,
  }));
}

The same query without max_mev_share_pct typically returns 2-3x more rows on a busy hour — but the dropped rows are exactly the ones you don't want to size into.

What to filter at

The right max_mev_share_pct depends on the play.

Sniper bots and fresh-launch entries (token under ~10 minutes old) — leave it off or set it loose (40%). Brand-new tokens haven't been sandwiched yet because the bots are still calibrating, so MEV share is naturally low; if it's already high on a 5-minute-old token, something is funny.
Scanner for momentum to swing trade — 25% is a sane default. Cuts wash but doesn't over-filter legit pumps that always attract some MEV.
"Is this token still alive?" liveness check — 50%+ MEV share over 4h is a strong "no." Real traders have left, what remains is bots eating each other.

How this compares to alternatives

Most public Solana data sources don't separate MEV at all — Dexscreener, Birdeye, and Jupiter volume figures are gross of MEV. You can post-filter their feeds yourself if you have your own classifier and the raw swap stream, but at that point you've built mc-tracker again.

A handful of analytics platforms attempt to flag wash trading at the wallet level (clustering wallets that round-trip with each other), which is a different problem — it catches volume bots farming chart positions, not sandwich bots. Both kinds of noise inflate volume; both deserve their own filter. MadeOnSol's mev_share_pct is specifically the sandwich layer; for the cluster/wash side, see our bot detection writeup.

Tier access

What "MEV volume" actually is on Solana

The shape we care about here is the classic sandwich: a bot frontruns a victim's swap on a specific pool, then backruns it in the opposite direction in the same slot, pocketing the slippage. The bot's two legs (the buy and the sell) both show up as on-chain swaps and both get counted by naive volume aggregators. So one organic swap shows up as three swaps' worth of "volume."

There are other patterns — JIT liquidity, statistical arb bots running tiny same-block round-trips — but on Solana memecoin pools the dominant noise source is plain sandwiching. It's particularly bad on pump.fun and PumpSwap, where the constant-product curve makes slippage extraction trivial.

How MadeOnSol classifies swaps

The classifier lives inside mc-tracker, the service that owns canonical token state. Every swap that comes off our DEX firehose is checked against a per-pool ring buffer of the last 50 trades. A trade is tagged mev_suspect when:

The same wallet executed an opposite-direction swap on the same pool within a few seconds, AND

The counterpart swap was at least 50% the size of the current swap (drops dust noise), AND

The current swap is at least 0.05 SOL (skip pure dust)

In a typical buy-buy-sell sandwich, this catches the sell backrun cleanly — the bot's exit swap happens on the same pool, opposite the buy it just executed. The frontrun leg itself usually escapes the tag (we haven't seen the matching backrun yet), but for volume accounting we don't double-tag — we want to count the bot once, not zero times and not twice. The conservative one-leg tag is the right call.

Once tagged, the swap:

Gets added to cumulative_mev_volume_usd instead of cumulative_organic_volume_usd.

Is excluded from the VWAP that drives the headline price. MEV-tagged trades are slippage artefacts, not honest market prices.

Is excluded from last_price_usd updates — the pre-MEV price is more honest than the post-sandwich extraction price.

That last bit matters. If you've ever wondered why MadeOnSol's MC stays stable through a flash sandwich while Dexscreener spot jumps wildly, this is why. Sandwich bots set last-trade prices that don't reflect what a normal buyer would pay; we don't honor them.

The API surface

Two endpoints expose the split.

GET /api/v1/token/{mint} — windowed deltas

{ "token": { "mint": "...", "vwap_price_usd": 0.00041, "market_cap_usd": 412_000, "mc_change_pct": { "5m": 8.2, "15m": 22.1, "1h": 41.7, "2h": 39.2, "4h": 12.8 }, "volume_usd": { "5m": 4200, "15m": 18200, "1h": 81000, "2h": 142000, "4h": 290000 }, "mev_volume_pct": { "5m": 12.1, "15m": 18.4, "1h": 22.7, "2h": 27.1, "4h": 31.9 }, "history_age_seconds": 14400 } }

volume_usd is organic-only USD volume per window. mev_volume_pct is the MEV share of total volume per window — mev / (organic + mev). Windows are only present once the token has been tracked long enough; history_age_seconds reports the available coverage (capped at 4h 5m).

GET /api/v1/tokens — discovery with max_mev_share_pct

The PRO+ token scanner endpoint computes mev_share_pct over cumulative tracked volume per row, so you can filter tokens whose MEV layer is in a healthy band:

curl -H "Authorization: Bearer msk_..." \ "https://madeonsol.com/api/v1/tokens?min_volume_1h_usd=20000&max_mev_share_pct=25&sort=last_trade_desc&limit=50"

That's a meaningful filter: "give me tokens trading more than $20K/h in real volume, where bots aren't more than a quarter of total flow." Drop max_mev_share_pct=15 if you want only clearly-organic movers. If you're polling this scanner on a tight loop, read your remaining call budget straight from the response instead of guessing — we cover the pattern in reading your quota from the /v1/me endpoint.

Endpoint	BASIC	PRO	ULTRA
`/api/v1/token/{mint}` (volume + mev split)	yes	yes	yes
`/api/v1/token/batch` (volume + mev split)	yes	yes	yes
`/api/v1/tokens` scanner (with `max_mev_share_pct`)	—	yes	yes

Your Memecoin Volume Number Is Lying: Strip MEV at the Data Layer