> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/resources/partnerships/coverage.md).

# Coverage

ether.fi users can purchase cover from [Nexus Mutual](https://nexusmutual.io/), a decentralized insurance alternative. They have added the following Bundled Protocol Cover listings to their dApp.

### **ether.fi Liquid Bundled Protocol Cover**

Nexus Mutual offers protection against smart contract risk across EigenLayer, Ether.fi, Morpho Blue weETH / WETH market, Pendle Finance, Sommelier Finance, and Uniswap V3, which is bundled into one Cover NFT.

* [Purchase ether.fi Liquid Bundled Cover on Nexus Mutual](https://app.nexusmutual.io/cover/buy/get-quote?productId=150)
* [Learn more about the protections included in Nexus Mutual's ether.fi Liquid Bundled Protocol Cover (PDF)](https://drive.google.com/file/d/1uKKTcJ4I1PgrZyK88GK9jtP4AX_Cz9Ab/view?usp=sharing)

### EigenLayer + ether.fi + Pendle Bundled Protocol Cover

Nexus Mutual offers protection against smart contract risk across EigenLayer, Ether.fi, and Pendle, which is bundled into one Cover NFT.

* [Purchase EigenLayer + ether.fi + Pendle Bundled Cover on Nexus Mutual](https://app.nexusmutual.io/cover/buy/get-quote?productId=143)
* [Learn more about the protections included in Nexus Mutual's EigenLayer + ether.fi + Pendle Bundled Protocol Cover (PDF)](https://drive.google.com/file/d/14f44-CONnS9tWQyztbHW-_nAyRQjVVc8/view?usp=sharing)


---

# 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://etherfi.gitbook.io/etherfi/resources/partnerships/coverage.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.