# Pump.fun Launch Collector (`rhined/pump-fun-launch-collector`) Actor

Every new pump.fun coin, priced from the second it's created. Reads the bonding curve on-chain and samples on a timer, so coins that die stay in your data.

- **URL**: https://apify.com/rhined/pump-fun-launch-collector.md
- **Developed by:** [JJ Stowell](https://apify.com/rhined) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Pump.fun launch collector

Every new pump.fun coin, priced from the second it is created.

Around 20,000 coins launch on pump.fun every day. This watches them being born and records what happens next — market cap, how much SOL people put in, and how much the creator bought themselves — sampled every few seconds from the moment of creation.

### What you get

| Column | What it means |
| --- | --- |
| `symbol` / `name` | The coin |
| `ageSeconds` | How old it was at this reading |
| `marketCapUsd` | Market cap in dollars |
| `changeFromCreationPct` | Move since the launch price |
| `solInCurve` | SOL that has actually gone in |
| `devBuySol` | What the creator bought themselves |
| `devSharePct` | The creator's share of all money in |
| `graduated` | Whether it has left the bonding curve |
| `mint` / `pumpFunUrl` | Address, and a link to the coin |

A typical row:

| symbol | age | market cap | change | SOL in | dev bought | dev share |
| --- | --- | --- | --- | --- | --- | --- |
| Trio | 15s | $6,240 | +247.7% | 29.26 | 1.778 | 6% |
| TISUKI | 16s | $2,010 | +0.4% | 48.43 | 48.285 | 100% |

Those two rows are the reason people want this. Trio pulled in 29 SOL from real buyers in fifteen seconds. TISUKI's 48 SOL was *all the creator's own money* — the dev share column says so instantly.

### Two things that make this different

**Prices come off the chain, not from an API.** pump.fun's own price field is wrong by tens of thousands of times on a minority of coins — one reported a $124M market cap on a coin its own API valued at $2,253. This reads the bonding curve account directly and matched the creation event to within 0.0000% when tested.

**Sampling runs on a timer, not on trades.** Feeds built from trade history have a hole shaped exactly like the answer: a coin that dies stops trading, so it stops producing rows and quietly disappears. Here every tracked coin is priced on a fixed clock whether anyone trades it or not, so the dead ones stay in your data.

That second point matters more than it sounds. A dataset assembled from trades tells you about the survivors. This one tells you what actually happened.

### Settings

| Setting | Default | Notes |
| --- | --- | --- |
| How long to run | 10 min | Longer catches more launches |
| Follow each coin for | 20 min | Each coin is priced for this long after creation |
| Seconds between readings | 10 | Lower is finer and costs more |
| Only coins with real activity | on | Skips the ~70% that never trade at all |
| Minimum SOL in the curve | 1 | What counts as "real activity" |
| Max coins at once | 200 | Ceiling so a launch storm can't run away with credits |

### What people use it for

- **Research** — how launches behave in their first minutes, and how often they die
- **Screening** — spotting coins pulling real money in, versus a creator funding their own chart
- **Backtesting** — a clean history that includes the failures, which most feeds silently drop

### Honest notes

About 70% of launches never receive a single trade. The filter is on by default so you are not paying for rows about coins nobody touched — turn it off if the death rate is what you are studying.

This is a data tool. It reports what happened; it does not predict anything and makes no claim that trading on it is profitable.

# Actor input Schema

## `runMinutes` (type: `integer`):

Minutes to keep listening for new coins. Longer runs catch more launches.

## `trackMinutes` (type: `integer`):

Each coin is priced for this many minutes after it is created, then dropped.

## `sampleSeconds` (type: `integer`):

How often every tracked coin is re-priced. Lower gives finer detail and costs more.

## `liveOnly` (type: `boolean`):

About 70% of launches never get a single trade. Leave on to skip them; turn off if you are studying how often launches die.

## `minSolInCurve` (type: `integer`):

A coin counts as active once this much SOL has gone in. Ignored when the filter above is off.

## `maxCoins` (type: `integer`):

Ceiling on the watchlist so a launch storm cannot run away with your credits.

## Actor input object example

```json
{
  "runMinutes": 10,
  "trackMinutes": 20,
  "sampleSeconds": 10,
  "liveOnly": true,
  "minSolInCurve": 1,
  "maxCoins": 200
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("rhined/pump-fun-launch-collector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("rhined/pump-fun-launch-collector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call rhined/pump-fun-launch-collector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rhined/pump-fun-launch-collector"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7vcMNmHvP325wVuBZ/builds/3lvgWEQxRANMfqSZD/openapi.json