> For the complete documentation index, see [llms.txt](https://lt0-2.gitbook.io/degenc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lt0-2.gitbook.io/degenc/core-features/editor.md).

# AI-Powered Insights

### On-Chain Analytics

Advanced real-time insights on digital asset performance, market trends, and sentiment.

### Terminal

Personalized tools for tracking portfolios, visualizing market data, and creating shareable insights. Build complex charts and dashboards with ease by simply asking our AI agent to do it for you.

### Alpha Generation

Tailored strategies and wallet tracking to identify potential investment opportunities.

### Co-Pilot

Proactive AI companion that helps you understand market movers and position accordingly. Our copilot will come in many forms, and will be accessible through our web app (degenc.app) or through social bots (i.e. Telegram) and other future integrations.


---

# 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://lt0-2.gitbook.io/degenc/core-features/editor.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.