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

# For Program Operators

This section is for institutions enabling cover on a DeFi position: vault operators, structured-product providers, treasury managers, and partner protocols passing protection through to their own programs.

{% hint style="info" %}
In the MVP, enabling cover is **permissioned**. Program operators complete institutional onboarding (including AML/sanctions screening and eligibility checks) before they can request a quote or hold a Cover Token. Staking, by contrast, is permissionless. See [For Stakers](/for-stakers.md).
{% endhint %}

### What you'll find here

* [How Coverage Works](/for-program-operators/how-coverage-works.md) walks through the enablement flow end to end.
* [Cover Tokens](/for-program-operators/cover-tokens.md) explains what you receive when cover is enabled: an ERC-7621 Cover Token that records your active coverage, and how claims are handled.
* [Pricing](/for-program-operators/pricing.md) describes, at a high level, how premiums reflect the risk components Firelight monitors in real time.
* [Claims Process](/for-program-operators/claims-process.md) details how a covered incident becomes a payout, with no claim-submission step required of the program operator.
* [Supported Protocols and Markets](/for-program-operators/supported-protocols-and-markets.md) lists the markets eligible for coverage at launch.

### What you need to know before enabling cover

Cover is enabled for a fixed 30-day period and cannot be cancelled mid-period. Premium is paid upfront. You receive an on-chain Cover Token representing your active coverage for that period, which you hold until expiry. When a payout is triggered, you receive the proceeds as the holder of the on-chain Cover Token and pass them through to depositors in the underlying vault under the vault's terms.

Coverage applies only to markets you explicitly schedule when cover is enabled. If your strategy moves into a non-declared market during the period, that allocation is uncovered until you renew with an updated declaration. See [Periods and Coverage Cycles](/core-concepts/periods-and-coverage-cycles.md).

### Typical program operator journey

1. Complete institutional onboarding (one time).
2. Review the approved markets and current available limits in the Cover Registry.
3. Request a quote specifying markets and coverage amounts.
4. Approve premium spending from a prefunded wallet.
5. At the next period boundary, the matching engine allocates capacity and settles premium.
6. Coverage activates and the Cover Token is issued to your address.
7. If a covered incident occurs, valid coverage is included automatically, no claim filing required.


---

# 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.firelight.finance/for-program-operators.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.