> For the complete documentation index, see [llms.txt](https://docs.neglect.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neglect.trade/products/trading-terminal.md).

# Trading Terminal

Professional-Grade Solana Trading for Bonded Tokens

Neglect is a mobile-first Solana trading terminal designed specifically for bonded tokens. Built for retail traders navigating Solana’s volatile trenches, Neglect emphasizes sustainability, transparency, and advanced discovery tools to help you discover Solana's long tail assets before they trend.

<figure><img src="https://237997104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXaJ5K5vRNOTSFBUYmlVJ%2Fuploads%2FWkMsGjwcZ6xjf6Egnf2V%2F1500x500.jpg?alt=media&amp;token=8090a5a9-654e-4cd3-a15c-dc95915d7c6d" alt=""><figcaption></figcaption></figure>

Why Neglect?

Solana’s token trading ecosystem is a PvP (Player vs. Player) environment defined by:

* Insider manipulation and sniping bots
* Scam-prone token launches and rugs
* Rapid pump-and-dump cycles
* Burnout from capital swings and emotional stress

Neglect aims to make this battleground more navigable with:

* Competitive, sustainable, and nuanced tooling
* Mobile-friendly execution
* Smarter token discovery
* Leverage trading to amplify edge

### Unique Features of Neglect:

Neglect isn’t just another trading terminal; it’s a focused, data-driven strategy tool for traders who want to maximize profitability and minimize risk.


---

# 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.neglect.trade/products/trading-terminal.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.