> For the complete documentation index, see [llms.txt](https://docs.basedbot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.basedbot.app/web-app/webapp/pulse.md).

# Pulse

Pulse is a real-time token feed that surfaces new and trending tokens as they appear on supported chains. It is designed for traders who want to catch tokens early.

<figure><img src="https://3562303282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5bUac2iI3Ns1M4sRzbQ%2Fuploads%2Fgit-blob-d01cb4483e32f533981b6e68975f1590a382a59b%2Fwebapp-pulse.png?alt=media" alt=""><figcaption><p>Pulse — real-time token feed</p></figcaption></figure>

## Live Feed

The Pulse page displays a continuously updating stream of tokens, including:

* **New launches** -- tokens that just deployed or started trading
* **Trending tokens** -- tokens gaining volume and momentum
* **Bonding curve tokens** -- tokens still in their bonding curve phase, shown with a progress indicator displaying how far along the curve they are

Each card in the feed shows the token name, chain, age, price, market cap, and volume.

## Quick Buy

Every token in the Pulse feed has a Quick Buy button, allowing you to enter a position immediately using your default buy settings for the active chain.

## Chain Filter

Use the chain filter at the top of the page to focus on tokens from a specific chain, or view all chains at once.


---

# 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://docs.basedbot.app/web-app/webapp/pulse.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.