> For the complete documentation index, see [llms.txt](https://docs.junkipedia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.junkipedia.org/getting-started/reviewing-tracked-content/searching-for-issues.md).
# Searching For Issues
The simplest way to look for issues is to search for key words. From the "All Issues" page, simply type a key word into the search box and hit enter.
For example, I can enter "elections" to help me track misinformation related to relating to that topic. I am then shown a list of issues that contain this key word.
#### Multiple Keywords
I can find more results by trying related key words such as "voting," "vote," and "ballot" one at a time. However, if I enter all of these key words at once I will get fewer results because the system will try to match all of these words. Continue reading [Filtering Issues](/getting-started/reviewing-tracked-content/filtering-issues.md) to learn about more options for sifting through content that has been collected into the system.
---
# 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.junkipedia.org/getting-started/reviewing-tracked-content/searching-for-issues.md?ask=&goal=
```
`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.