> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/discover-and-trade/12-spawn-feed.md).

# 12. Use the live Spawn Feed

Discover verified launches, understand card metrics and interpret buy activity animations.

**Open:** [Spawn Feed](https://spawnmeme.com/launchpad), or the feed section on the homepage. No account or wallet connection is needed to browse.

## Browse the feed

1. Choose a category.
2. Inspect a token card's name, ticker, image and available live metrics.
3. Open the card and compare the full mint address with the project's official source.
4. Read the token page before choosing whether to trade or use a community tool.

| Category         | What it shows                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Fresh Spawns** | Recorded launches, with paid boost ordering and possible official-token pinning; not a strictly chronological list |
| **Hot Spawns**   | Tokens with active paid boosts, ordered by boosts                                                                  |
| **Graduating**   | Active curves with readable progress, closest to graduation first                                                  |
| **Top Spawns**   | Tokens with readable estimated market cap, highest first                                                           |

These tabs differ from the Buy Bot's organic Trending board and from wider Solana Markets rankings.

## Live updates and card animation

The homepage and feed page update from the shared launch feed. Newly registered launches should appear as the data refreshes. A brief card glow indicates a newly detected supported buy event. It is a visual activity cue, not a guaranteed price move or a reason to buy.

Updates depend on a completed launch record, data services and the active browser session. Hidden pages, slow connections and indexing can delay a change. The animation is brief and repeated events can be deduplicated.

## Read the numbers correctly

Market cap is an estimate, not available exit liquidity. Curve percentage reflects the token's actual curve configuration, not a universal SOL target. Missing metrics mean the data was not available; they should not be read as zero. USD values depend on an external SOL price.

## Troubleshooting

| Problem                           | Resolution                                                                                                                                                  |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New token missing                 | Confirm the transaction and registration; use **Fresh Spawns** and then refresh. A draft alone is not a feed entry.                                         |
| Token appears in another tab only | Check category rules; **Hot Spawns** requires active boosts.                                                                                                |
| New token is not first            | Paid boosts and official pinning affect Fresh ordering.                                                                                                     |
| No glow after a buy               | The event may already have been seen, be delayed, or fall outside supported detection. Verify the transaction on-chain.                                     |
| Loading market caps               | Wait for live stats or retry after connectivity recovers.                                                                                                   |
| Feed stays frozen                 | Preserve any pending transaction receipts and follow [browser troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md). |

Browsing and card animations are free. Trading and [paid boosts](/spawnmeme-docs/feature-guides/telegram-and-promotion/31-boosts.md) are separate actions.

## Looking for project pages?

The Feed lists tokens. [Projects](/spawnmeme-docs/feature-guides/create-a-project/47-projects.md) lists published creator pages, including projects that have not launched a token.

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/discover-and-trade/12-spawn-feed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.