> For the complete documentation index, see [llms.txt](https://eigenphi-1.gitbook.io/classroom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eigenphi-1.gitbook.io/classroom/eigenphis-methodologies/why-mev.md).

# Why MEV?

To tackle it head-on with MEV, the gravest crisis of DeFi is facing at the moment; EigenPhi chose MEV-related data, which encompasses the most accurate and authentic data regarding DeFi liquidity.

MEV transactions are the most complicated and most concerning transactions of DeFi. Few handy tools on the market can be used to closely examine the massive capital invested into MEV. Based on our data, on average, there are 5 asset transfers in one MEV transaction.

By targeting MEV, EigenPhi looks to enhance the efficiency of the market and build a healthier and more robust DeFi ecosystem, **ultimately empowering users with information apparatus to explore the new DeFi world.**


---

# 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://eigenphi-1.gitbook.io/classroom/eigenphis-methodologies/why-mev.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.