> For the complete documentation index, see [llms.txt](https://docs.daisy.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daisy.so/core-tools/explore/search.md).
# Search
**Find exactly what you're looking for in the daisy library**
Discover content across the entire daisy ecosystem by keyword search. With search, you can comb through both your own creations and the broader community's outputs, finding Shots and Pods to try out. This comprehensive search capability means you can explore thousands of Shots and Videos. Finding exactly what you need for your next project.
***
## How to Search
### Step-by-Step Process
***
## Search Best Practices
### ✅ Do this:
* Combine multiple filters for better results
* Try different keywords and synonyms
* Browse regularly to discover new content
* Save content you like for future reference
### ❌ Avoid this:
* Using too many filters at once initially
* Limiting yourself to one content type
* Forgetting to clear filters between searches
***
**Ready to search?** Head to the [Explore page](https://app.daisy.so/explore) and start your search, or check out [**Filters →**](/core-tools/explore/filters.md) to learn about advanced filtering options.
---
# 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.daisy.so/core-tools/explore/search.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.