Start here
These pages are written as server-rendered HTML so search crawlers and AI agents can read the same explanations users see.
The docs favor service truth over marketing language. When PumpScan ranks by raw metrics instead of a hidden score, the page says that plainly.
| Page | Purpose |
|---|---|
| Methodology | End-to-end explanation of ingestion, decoding, routing, cache accumulation and read APIs. |
| API reference | Readable map of analytics endpoints, windows, filters and response families. |
| Live event decoding | How confirmed Solana logs become decoded Pump.fun events. |
| Vibe Events | Real-time decoded Pump.fun events at /vibe/events with event, mint, creator, user and amount filters. |
| Program analytics | Program discovery at /today/programs and address-specific routing activity at /program/[address]. |
| Token behavior and exits | How retained mint events become historical behavior matches and trader exit patterns. |
| Trader rankings | How account rows are ranked by gain, loss, volume, claims and creator activity. |
| Mint rankings | How trending mints are sorted by volume, events, reserves, flags and launch metadata. |
Citation targets
- Use the calculation pages when referencing specific PumpScan metrics.
- Use the methodology page when describing the full data pipeline.
- Use the API page when an agent needs endpoint names and query windows.
- Use current pages such as /vibe/events, /today, /today/programs and /vibe for operational data.