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

# Pricing

Firelight prices coverage from a per-market premium rate that reflects the risk components the protocol monitors in real time. This page explains, at a high level, what drives a premium and what is published on-chain. It avoids formulas. The methodology reference is in [Risk and Pricing Model](/risk-and-pricing-model.md).

### What drives the premium

A market's premium reflects Firelight's live view of that market's risk, built from two independent sides:

* **Economic side.** Market-driven risk. The protocol monitors a near-term bad-debt view (how likely a bad-debt incident is over the next 30 days, and how severe it would be) and a structural graph overlay that watches relationships between collateral and the loan tokens it backs. Both contribute to the economic component of the premium.
* **Technical side.** Code and infrastructure driven risk: smart contract bugs, oracle and integration fragility, upgrade patterns, and chain-level posture. This is scored separately and forms the technical component of the premium.

Across both sides, signals are organized across the same four risk components and updated continuously:

| Component  | Example signals that move the rate                              |
| ---------- | --------------------------------------------------------------- |
| Blockchain | Network incidents, finality and validator health                |
| Protocol   | Audit status, exploit history, oracle and admin-control changes |
| Asset      | Volatility, liquidity depth, depeg behavior                     |
| Strategy   | Leverage, composition, liquidation headroom                     |

On top of the expected cost of covering a market, the premium includes the cost of the capital backing it. Higher monitored risk on either side means a higher rate. A critical signal (such as an active exploit or a lapsed audit) can remove a market from coverage entirely.

### What is published on-chain

For each approved market, the Cover Registry publishes, refreshed every 30 days:

| Parameter                   | Description                                                                |
| --------------------------- | -------------------------------------------------------------------------- |
| Base premium rate           | The market's premium as a percentage of coverage                           |
| Available limit by protocol | How much coverage capacity remains available for that protocol this period |

Within a period the published rate is fixed for program operators. Between periods it can move as the monitored risk view updates.

### From rate to program operator premium

A program operator's premium is the coverage-weighted blend of the per-market rates across the markets they select, applied to the coverage amount for the 30-day period and paid through the vault operations. The quote shows the blended rate, the per-market rates that drive it, and the total premium due.

{% hint style="info" %}
Numbers in any worked example are illustrative. Published rates and available limits vary by market and period, and the detailed pricing methodology is under active calibration. Cover Registry values take precedence.
{% endhint %}

### Capacity limits

Coverage on a market is available only up to the published available limit for that protocol. If a program operator's requested allocation exceeds the available limit, the matching engine reduces the allocation to what remains and either reallocates within the program operator's declared set (if capacity exists) or returns a partial match with a proportional premium refund. Markets not on the approved list cannot be quoted.

### Where to read next

* [Risk Pricing Framework](/core-concepts/risk-pricing-framework.md) for the high-level model.
* [Risk and Pricing Model](/risk-and-pricing-model.md) for the methodology reference.
* [Claims Process](/for-program-operators/claims-process.md) for how a covered incident becomes a payout.


---

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