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

# Trade Ideas

Trade Ideas is the catalog of Sterling's current ideas, long and short, across every company covered. Open **Trade Ideas** in the sidebar.

## Browsing

Ideas appear as cards grouped by how recently they were published. Each card shows the direction (long or short), the date, performance since publication, and the upside to the target. **Read in analyst** opens the thesis in the Analyst, where you can question it.

The prompt box at the top, **Ask Terminal about any trade idea**, sends whatever you type to the Analyst.

## Filtering

* **Company**: type a name.
* **Sectors** and **Themes**: pick one or more. Search themes by name.
* **Sources**: the kinds of evidence behind the idea.
* **Performance**: **Big Upside**, **Moderate Gains**, **Stable**, or **Neutral**.

Trade ideas are research, not instructions. They are published with their reasoning and sources so you can judge them; Sterling does not trade on your behalf.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sterlinglabs.co/research/trade-ideas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
