The same people launch again and again. Cookin keeps the whole back catalogue for every deployer: how many launches graduated, how high they went, and how a typical one ended rather than the best one.
| Field | Meaning |
|---|---|
summary.total_deployed |
Tokens this deployer has launched. |
summary.bond_rate |
Share of launches that graduated. |
summary.best_ath_mcap |
Highest peak market cap across all launches. |
summary.ath_mcap_percentiles |
The spread of peaks, so one lucky launch is visible as one. |
summary.ath_milestones |
How many launches ever reached each market cap rung. |
data[] |
Every token: launch time, whether it graduated, its own peak. |
$ curl "https://api.cookin.fun/v1/devs/<wallet>/tokens?limit=5"
{
"data": [
{ "mint": "...", "has_migrated": true, "ath_mcap": 412000 },
{ "mint": "...", "has_migrated": false, "ath_mcap": 9800 }
],
"summary": {
"total_deployed": 57,
"bonded_count": 2,
"bond_rate": 3.51,
"best_ath_mcap": 412000,
"ath_mcap_percentiles": { "p50": 7400, "p90": 48000 }
}
}
Pay per call in USDC on Solana with x402, from $0.01 and no account, or use a Pro key at 1 SOL per 30 days. A call that errors is never charged. Full price list on the x402 page.
Launches are keyed to the deploying wallet, so a serial launcher's record follows them from token to token. The percentiles matter more than the best number: a deployer with one 400k launch and a 7k median is a different bet from one with a 40k median, and the headline hides that.
https://api.cookin.fun/mcp, or locally with
npx -y @cookinfun/mcp.
The share of a deployer's launches that graduated to Raydium or PumpSwap. Most deployers sit in low single digits, so the number is only useful next to the sample size, which the response also returns.
As far as Cookin has tracked that deployer, which is every Pump.fun launch since the index started.
Yes. A deployer's record changes only when they launch again, so one call a day per deployer is plenty.