> For the complete documentation index, see [llms.txt](https://bullnbear.gitbook.io/trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bullnbear.gitbook.io/trade/readme.md).

# BullNBear — Trade & Launch

BullNBear is an all-in-one on-chain trading platform and launchpad built to help users discover, trade, track, and launch tokens from one place.

The platform combines a real-time trading terminal, token discovery tools, wallet tracking, copy trading, trending analytics, portfolio management, rewards, and token creation into one connected ecosystem. Users can monitor new launches, follow market momentum, manage assets, and trade across supported pools directly through BullNBear.

In fast-moving on-chain markets, timing matters. BullNBear is built for traders who want faster discovery, cleaner execution, and better visibility over live token activity, while also giving projects the tools to launch directly through the platform.

> BullNBear’s mission is to build a complete launchpad and trading ecosystem where users can discover opportunities earlier, trade with confidence, and participate in a platform designed around speed, transparency, and community growth.

BullNBear brings together every major part of the on-chain trading journey in one platform.

**BullNBear is built as a complete ecosystem for both traders and projects.**


---

# 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://bullnbear.gitbook.io/trade/readme.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.