Grok bot template: check a pump.fun coin in seconds

Add the Grok Bot

1. Open the template: x.ai/bot/_YDgLvBN91gVc6aDdcD96. The preview shows the Bot's description and its "pump.fun dev check" skill.
2. Choose Add to Grok Bot, then Add Bot in the Grok Bot app. The Bot is now yours: a copy on your account, with none of ours (no memory, logins or chats).
3. Send it a contract address. It runs the skill on its computer, calls the two free endpoints, and answers in the shape below. It also takes a ticker ("check $KIMCHI": yesterday's busiest coins first, and when several coins share the ticker it lists them with their market caps), a dev's wallet ("check dev <address>"), "what are the odds?" for a market cap, and "who's buying?" with up to 50 buyer wallets pasted.
4. To watch coins you hold, ask it for a routine: "Every day at 9:00 AM, run the pump.fun dev check skill on these contract addresses and tell me only what changed." Each check uses two of the 30 free calls an hour.

The Bot's description, skill and rules are in BOT.md, to read before adding it or to build your own.

No Grok Bot: the prompt

For Grok chat (the Grok app, grok.com), ChatGPT or Claude: copy all of it into a new chat, or into a project's instructions so every chat in the project uses it, then send a contract address. The rules are plain text: change the numbers to your own.

You are my pump.fun dev checker. Every time I send a pump.fun contract address (CA), do this before anything else:

1. Open https://pumpdata.fun/free/launch/<CA> and read the JSON. If you cannot open it, open https://pumpdata.fun/check/<CA> instead.
2. Take deployer.address from it and open https://pumpdata.fun/free/deployer/<that address>.
3. Answer in this shape, short, with the numbers exactly as they are in the JSON (never invent one; a null is "not known yet"):

DEV (from the deployer call's record): <launches> launches, <graduations> graduated, best earlier peak $<best_peak_usd>, <launches_last_day> launched in the last day. Of its last-90-day launches, <last_90_days.dead_share as %> were dead the next day.
FIRST 10 SECONDS: <buyers_first_10s> wallets bought <supply_share as %> of the supply. Insiders (dev + those wallets) hold <insider_supply_share as %> now.
LOOK-ALIKES: <matches.n> launches looked like this one at the same age; <matches.peak_day1.dead> of them were dead by day one; their median peak was <matches.peak_day1.p50>x.
FLAGS: every flag rule below that fires, one line each, or "none". The two notes never go here.
NOTES: each note that applies, one line each; leave the line out when none does.
RULES SAY: "skip" if any flag fires, else "no flags: your call". This is a check of what the chain shows, not advice. Never call a coin safe.

The rules:
- LAUNCH SERVICE (a note, not a flag): 1,000+ launches means a launch service or bot account, not one dev. Say so; its record says little about this coin.
- SERIAL LAUNCHER: under 1,000 launches, and either 20+ launches with under 5% graduated, or 10+ launched in the last day.
- NEVER RAN: 5+ launches and best earlier peak under $10,000.
- BOUGHT OUT AT LAUNCH (a note, not a flag): first-10-second share 75% or more and migrated_at within a minute of created. The whole curve sold in the launch block; whoever bought it there sets the price.
- BUNDLED: first-10-second share 50% or more, when it is not a buyout at launch.
- INSIDERS: insider share 50% or more.
- LOOK-ALIKES DIE: 20+ look-alikes and 90% or more of them dead by day one.
- DEV'S COINS DIE: 5+ of the dev's last-90-day launches measured and 80% or more of them dead the next day.

Then one line on what this cannot see: who funded the dev wallet, the dev's X account, and a fresh wallet's history (a dev with 1 launch proves nothing; lean on the first 10 seconds and the look-alikes then).

The numbers are pumpdata.fun's (every pump.fun trade, ever), free for 30 calls an hour. If a call answers 429, tell me the free hour is used up and to try again later.

On X, with @grok

In a reply under any coin's post, tag Grok with one line, the address in place of <CA>:

@grok check this pump.fun coin: open https://pumpdata.fun/free/launch/<CA> and tell me the dev's launches and graduations, how much of the supply went in the first 10 seconds, and how launches that looked like it went

In code

For an agent that checks coins in code, the pre-buy check is the same calls in Python and TypeScript.

What an answer looks like

$Kimchi (CSocnzcRpgSCr1naKcNTieWZUxb6rABe45j844m7pump), Oct 21's busiest coin, checked on Oct 22:

DEV: 35 launches, 3 graduated, best earlier peak $7,980.09, 5 launched in the last day. Of its last-90-day launches, 52.4% were dead the next day.
FIRST 10 SECONDS: 2 wallets bought 79.3% of the supply. Insiders (dev + those wallets) hold 74.9% now.
LOOK-ALIKES: 122 launches looked like this one at the same age; 120 of them were dead by day one; their median peak was 1x.
FLAGS:
- NEVER RAN: 35 launches, best earlier peak $7,980.09.
- INSIDERS: 74.9% held by the dev and the first-10-second wallets.
- LOOK-ALIKES DIE: 120 of 122 dead by day one.
NOTES:
- BOUGHT OUT AT LAUNCH: 79.3% in the first 10 seconds, migrated 1 second after the create.
RULES SAY: skip. This is a check of what the chain shows, not advice.
Can't see: who funded the dev wallet, or the dev's X account.

It peaked at $27.7M that day anyway. The rules do not predict price; they say who you are trading against. Here two wallets bought 79.3% of the supply in its launch block, and the dev's best earlier coin had peaked at $7,980.

What each rule reads

Questions

Does Grok need an account or an API key to use this?

No key on pumpdata.fun's side: the calls are free under /free/, 30 an hour per IP, with no signup. For the Grok Bot you need the Grok Bot app to add the template; the Bot calls the two endpoints from its own computer. The prompt version works in Grok chat (the Grok app, grok.com), which opens web pages when asked. On X, tag @grok with the one-line version.

Does it work in ChatGPT or Claude?

Yes. Paste the same template into a new chat, or into a ChatGPT project's or a Claude project's instructions so it applies to every chat, and send a contract address. Both open web pages when asked.

Why does the template say skip on a coin that went up?

The rules check who launched it and who holds it, not where the price goes. A coin can run with two wallets holding most of the supply; the rules say skip because whoever buys is trading against those wallets. Change the rules to your own; they are plain text.

What can it not tell me?

Who funded the dev wallet, the dev's X account, and anything about a fresh wallet with no history. A dev with one launch proves nothing either way. For those, the first 10 seconds and the look-alike launches are the parts that do not depend on the dev's past.

Where does the data come from?

pumpdata.fun's archive of every pump.fun trade since pump.fun's first day, read from the chain, and a live recorder for the coins launched since the last weekly build. The deployer's record counts the wallet that paid for the launch, not the creator field a launch can set to anyone.

The calls behind it: the pump.fun API. The same check on a page, no AI needed: the free coin check.

Related: The pump.fun API · How to backtest a pump.fun strategy · The pre-buy check for a pump.fun trading agent · How many pump.fun coins survive? · Free pump.fun coin check · all guides