> For the complete documentation index, see [llms.txt](https://docs.onre.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onre.finance/for-insurers/regulatory-framework.md).

# Regulatory Framework

### Licenses and Regulation <a href="#pdf-page-mmjoz4sca7chavqvm8iq-licenses-and-regulation" id="pdf-page-mmjoz4sca7chavqvm8iq-licenses-and-regulation"></a>

On Re SAC Ltd. is [authorised and regulated](https://www.bma.bm/regulated-entities) by the Bermuda Monetary Authority (BMA).

#### Class F License Under the Digital Asset Business Act 2018

OnRe is licensed under Bermuda’s [Class F Digital Asset Business Act 2018](https://www.bma.bm/digital-asset-business), authorizing the issuance, sale, and redemption of digital assets, the provision of payment services using digital assets – including fund transfers – and the operation of a digital asset exchange. This regulatory approval enables OnRe to offer a comprehensive suite of digital asset services in a secure and compliant environment.

#### Class IIGB License Under the Insurance Act 1978

OnRe is licensed under a [Class IIGB (Innovative Insurer General Business) license](https://www.bma.bm/insurance-licensing) from the BMA. This authorizes OnRe to carry on general insurance business in an innovative manner, including the use of digital assets or cryptocurrency for insurance-related activities. The IIGB license provides a regulated framework for OnRe to underwrite, manage, and structure insurance solutions that leverage new technologies and digital asset infrastructure.

Registration Number 55347.


---

# 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://docs.onre.finance/for-insurers/regulatory-framework.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.
