> 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/arpro.md).

# arPro

**arPro** is an upgrade of arCore. It is an innovative new cover concept which will increase profits for coverage providers while reducing costs for end users. 

arPro features:

* Direct monthly coverage so that Armor doesn’t need to pay NFT stakers a markup or subsidize their costs with reward emissions
* Easy ability for contracts (both Protocols and arShields) to plug into the system to enable bulk coverage sales to protocols in addition to users
* Perpetual coverage so contract doesn't need to be pinged / bill doesn't need to be paid every month
* Ability to aggregate multiple protocol specific Layer 1 coverage provider.
* Ability to aggregate protocol agnostic Layer 2 coverage (utilizing Armor LPs as collateral). L2 can be cross leveraged to provide coverage for multiple protocols, thereby multiplying revenue.
* Hybridized cover: arLayer will have the ability to set the sequence of payouts in the case of a hack. 
  * Layers in parallel coverage (eg. 50% from L1 and 50% from L2)
  * Layers in series coverage (eg. 50% from L1a first; if exhausted, only then pay the overage with L2) 


---

# 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/arpro.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.