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

# FAQ - Buy Cover

## What is a cover?

A Cover is a decentralized alternative to an insurance policy. It is not the same as insurance because it is a permissionless process where anyone from the community can provide the required capital. The rules of the cover are executed by a smart contract on the blockchain.

## What is the role of Bright Union?

Bright Union is a protocol which helps customer buy and manage their covers from a single place. In case a claimable event happens , the risk platform and not Bright Union is liable for the payment of the claim. 

## What covers does Bright Union offer

The cover types are described on this page: <https://docs.brightunion.io/buying-coverage/cover-types>

## What determines Cover availability?

The risk platforms determine whether a cover for a certain protocol is added based on an admission or whitelisting process. Usually the (code) quality of the protocols before it is offered for sale. \
\
In order to buy a cover the community must have provided sufficient cover capital so claims can be paid in case of a claimable event. In case there is limited capital available it might not be possible to buy a certain cover or a higher price will be demanded.

## Who is responsible to pay a claim if the protocol I covered is hacked?

Once a claim is approved (link to claims process) the claim will be paid out from the capital provided by the community. Each risk platform has a different approach to managing and leveraging the capital provided by the community. &#x20;

##


---

# 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://docs.brightunion.io/faq/faq-buy-cover.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.