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

# Welcome to Notum

We Simplify DeFi

### [All Investments in One Space](/defi/types-of-defi-investments.md)

Notum aims to consolidate all information on available DeFi investments in the EVM space onto one user-friendly platform. There is no need for switching between multiple platforms to compare yields and rates. It's all brought together in one place.

### [Risk Assessment ](/risk-assessment/risk-assessment-framework.md)

By implementing risk assessment, Notum strives to create a more user-friendly environment for the DeFi market. We are confident that by simplifying the complex DeFi schemes and protocols functionality into easy-to-grasp components, we can encourage more people to adopt DeFi opportunities on a larger scale. This will result in a higher number of individuals prepared to embrace and utilize DeFi services, thus the future of finance.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notum.ai/welcome-to-notum.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
