> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/segments/magic-segments.md).
# Magic Segments
When you're starting out with Reo.Dev and want to quickly act on the data, Magic Segments on the Segments page are an excellent place to begin.
Magic Segments are pre-built by Reo.Dev to help you easily identify high-intent accounts in no time.
There are 5 magic segments:
1. **Accounts with De-anonymized Developers**: This segment displays only those accounts where developer profiles have been de-anonymized.
2. **High Developer Activity**: This segment identifies accounts with developers who are frequently active on product assets. It's worth your sales team's attention to spot potential sales opportunities.
3. **Accounts in Building POC Stage:** Accounts in this stage are experimenting with your features and building proofs of concept. Keep an eye on these accounts as they show high interest in your product.
4. **Accounts in Deployed Stage:** Shows accounts with signals indicating your product is live and in use
5. **Accounts Active on GitHub and Docs**: Accounts in this segment show strong technical engagement across your GitHub Repos and Docs. Activities on cross-functional channels most likely suggests high interest in your product.
---
# 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.reo.dev/segments/magic-segments.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.