PumpPill — token safety and measured outcomes

Whether the claim this client is sending is an active PumpPill membership, which tier it is, and when it renews. Answers 'am I signed in?' without touching any member data. An unauthenticated call is not an error - it answers signed_in=false. Nothing about the claim itself is ever returned.

The Robinhood Chain wallets this member follows: what each can move (capital), what it has done (record), what it has traded in the window (activity), and the events that fired. Requires a PumpPill membership. The client sends it as a header: Authorization: Bearer <your claim>, where the claim is the sign-in token on pumppill.org/premium. Two readings that are not interchangeable: CAPITAL is size - a balance read on chain, which says a wallet CAN move a pool, never that it is right. RECORD is history, given as counts (judged, wins) beside the chain's own base rate, because a percentage without its denominator is the thing this server does not ship. A wallet with no activity is one we have not seen move, not one that has gone quiet. A sell's size comes from the router's minimum-out, so it is a floor and never a profit figure.

Forward-measured outcomes across both chains: the share of logged tokens that doubled, reached 5x, reached 10x, or never moved. The honest part, and the reason this is worth citing: entry is the market cap at the MOMENT OF LOGGING, never backfilled, and LOSERS ARE IN THE DENOMINATOR. It is not a track record of picks and not a win rate for anyone who bought - it is what happened to a population of tokens after they were seen, with the method stated beside it. Recomputed hourly. One call an hour lands during the recompute and may take up to 45 seconds or return error='recomputing'; that same call warms the cache, so a retry a minute later is instant.

The premium call table - the Solana tokens PumpPill has logged for members, newest first, with the market cap at which each was logged and how far it has moved since. Requires a PumpPill membership. The client sends it as a header: Authorization: Bearer <your claim>, where the claim is the sign-in token on pumppill.org/premium. Each row is a token that cleared an attention filter: a promoter with real reach posted the contract, or a narrative it matches is moving. That is a filter on attention, NOT a prediction and NOT a recommendation to buy. 'Move since logged' is measured from the market cap at the moment of logging, which is not a price anyone was offered. Narrative and trend columns are deliberately not returned: they are inconsistently populated and must not be quoted as a signal.

How the chain measures, from PumpPill's own index, recomputed hourly with the method stated in the payload: tokens seen, how many carry a forward-measured outcome, how many doubled or reached 5x and 10x, how many crossed $100,000, and how many are quoted against a tokenized stock. Free to quote with attribution, and the payload carries its own computed_at - quote that, not the time you asked. Outcome counts are counts, not a success rate: entry is the market cap at the moment of logging, and the index covers what PumpPill has seen rather than everything that exists.

What one wallet has launched on Robinhood Chain, and how those launches went: the tokens, their liveness and liquidity, and which crossed $100,000. This is the question a launchpad buyer can act on - has this wallet done this before - and it is indexed almost nowhere else. Two wallets on this chain own 26,321 of 27,981 launchpad rows: those are factories or relayers, not operators, so a wallet above the launch ceiling deliberately gets no record rather than a headline reading 'this wallet launched 14,512 tokens'. A wallet with one launch also gets none: one launch is a fact about a token, not about a wallet. No win rate is computed - a 'crossed' row exists only because a token crossed, so the denominator would hold no losers.

Wallets whose first buy landed inside the early window of tokens that later crossed $100K, read off the chain's own feed, with the feed's base rate beside every rate. 🚨 A record is a fact about timing, not a forecast. meta.early_base_rate is the share of ALL judged tokens on the feed that crossed; a wallet's rate means nothing without it and must be quoted with it. The feed begins at meta.tape_since and the record does not reach back before that. Wallets are removed for spraying, for falling below the base rate on five or more judged entries, or for silence. realized_fill_eth, when present, is what the wallet's sells actually received on chain minus what it paid; when it is null the sells are still being read.

Tokens whose latest scan in the last 30 days found HIGH or CRITICAL structural risk, with the findings named. Each entry is a finding with evidence - a mint authority still open, a holder concentration, a launch pattern - not a verdict on where the price goes, and not an accusation about anyone. Use it to show what the current wave of bad launches looks like, never as a list to trade against.

Robinhood Chain's genuinely novel structure: memecoins quoted in TOKENIZED STOCKS rather than in a native coin. Pass a stock symbol (NVDA, SPY, TSLA) for the trading, unflagged tokens quoted in it with liquidity and the latest scan risk. Omit it for every stock with a count. This pairing exists on no other chain, so it is usually the part of a Robinhood Chain answer that a reader has never seen stated anywhere.

Names ONE Robinhood Chain contract for a ticker symbol - the question that actually costs people money, because a name can be deployed any number of times. The named contract is alive, holds at least $10,000 in its pool and is not flagged HIGH or CRITICAL. Every other contract using the name is returned as a COUNT (contracts_other), never a list, because publishing a list of impostor addresses is a menu. found=false means no contract using that symbol clears the gate, which is itself the answer.

The STORED safety read for one Robinhood Chain token (address = 0x + 40 hex): whether it can be sold, what is flagged on the launch, where the launch money went, and how far it has run from the market cap at which PumpPill first logged it. Answers in under 100ms from the last stored scan and NEVER triggers a new one. found=false is an honest miss - the token has not been scanned - not a clean bill of health. deep=true means the economics, lock, operator and thesis passes ran; without it only the structural checks did. A flag is a finding with evidence, not a prediction. 'peak' is the high since scanning began, which can be after logging, so a peak below the entry means the run happened before PumpPill saw it.

What a single wallet holds and what it has traded, off the chain's own feed. A sell's size is derived from the router's minimum-out, so it is a FLOOR and is never reported as profit - do not turn it into a P&L. Many addresses on this chain are routing contracts rather than people; a balance alone does not make an address someone.

Wallets holding at least 10 ETH or $50,000 in tokens, read as BALANCES on chain, not inferred from activity. Tiers are by dollars held, ETH and tokens together: mega, whale, mini (a wallet holding $100,000 of one of the chain's largest tokens is a mini whale whatever its ETH balance says) and large; positions_top names each wallet's three largest holdings. 🚨 This measures who CAN move a pool, never who is right and never who to follow. Most listed wallets hold rather than trade - of 1,967 wallets, 14 traded in a 30-day window and the ten largest made zero trades - so meta.trading_30d is part of the answer, not a footnote. sort='active' orders by trades instead of balance. Trade counts start from meta.trading_since, the moment PumpPill began recording the chain's feed, not from a fixed history.

Wallets the launch scan recorded among a token's first buyers, on tokens whose peak later reached 5x the scan cap, with the base rate beside every rate. 🚨 Read every wallet's hit_rate_5x against meta.base_5x, the share of ALL judged tokens that did 5x (about one in twenty). Wallets that spray more than a token a day, sit at or below the base rate, or go silent are removed with the reason on the row. Wallet identity showed no out-of-sample edge on Solana when it was tested; this is the honest answer to 'who was early', not a list of wallets to copy.

Any Solana token by mint (base58): holders, bundled-launch read, what the deployer still holds, socials, and meta.verdict - one plain-English sentence saying whether it trades, whether it can be sold, what the dev holds and how far it has run. Start from meta.verdict. The rest is the evidence behind it. A clean read is not a reason to buy: it means the structural checks found nothing, not that the token will hold its value.

What X has actually been saying about one contract address: how many posts name the contract in their own text, how many distinct accounts, their combined reach, whether it is accelerating, and - for each poster - what they have called before and how those turned out. Requires a PumpPill membership. The client sends it as a header: Authorization: Bearer <your claim>, where the claim is the sign-in token on pumppill.org/premium. Read the counts carefully. A mention counts only when the contract address appears in the post's TEXT; ticker-only matches are reported separately because a name is not a token. Accounts are labelled by RECORD, not fame: 'proven' means the account earned a place on PumpPill's roster by naming contracts early on tokens that later ran, 'known_bot' is our own bot verdict, and 'unknown' only means too little history to judge. This is a SAMPLE of X, not a firehose - so zero mentions means PumpPill did not see any, never that nobody is posting, and it is not a red flag on its own. On an EVM contract silence is simply normal: none of the contract mentions we have ever observed were EVM addresses. There is no sentiment or hype score here and there will not be one - the payload carries counts, reach and record, and nothing that predicts.