> For the complete documentation index, see [llms.txt](https://armorfi.gitbook.io/armor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://armorfi.gitbook.io/armor/features-and-highlights/flexible-smart-cover-system.md).

# A True Smart Cover Solution

Limitations of Nexus Mutual coverage:

* KYC required
* Coverage cannot be refunded or resold
* Coverage has to be purchased separately for each protocol, for set pre-specified amounts
* Coverage once purchased cannot be modified

## **The baby step**

NFTs tokenized coverage which removed KYC requirements and opened a secondary marketplace to resell coverage to possible buyers. However, it is still clunky UX and has the same remaining limitations as Nexus mutual.

## The ARMOR Leap

Armor provides a true smart coverage solution for dynamic coverage of user funds across various DeFi protocols. Armor automatically tracks user funds as they move across protocols in real time, and allocates exact amounts of coverage so that your funds are always protected. What's more, you only pay for the coverage amount you used, and for the time you used it for.


---

# 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://armorfi.gitbook.io/armor/features-and-highlights/flexible-smart-cover-system.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.
