> For the complete documentation index, see [llms.txt](https://docs.fira.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fira.money/guides/overview.md).

# Markets Overview

Fira is modular lending infrastructure. Each **market** is an independent instance with its own collateral, loan token, parameters, and risk profile.

## What Defines a Market

Every Fira market is defined by:

| Parameter                   | Description                                                          |
| --------------------------- | -------------------------------------------------------------------- |
| **Collateral asset**        | The token deposited by borrowers                                     |
| **Loan asset**              | The token borrowed against collateral                                |
| **Max LTV (Loan-to-Value)** | Maximum borrowing ratio                                              |
| **LLTV**                    | Liquidation LTV — the threshold at which positions can be liquidated |
| **Oracle**                  | Price feed determining collateral value                              |
| **Maturity**                | Term length for fixed-rate positions                                 |
| **Protocol fee**            | Fee charged by the protocol (in APR)                                 |
| **IRM**                     | Interest Rate Model governing rate discovery                         |

This modular design means Fira can support any pair of assets — stablecoins, yield-bearing tokens, LSTs, or governance tokens — each with parameters calibrated to the specific risk profile of that pair.

## V1 Market Types

Fira V1 introduces three market types, each serving different credit needs:

### Fixed-Rate Markets

Borrowers and lenders lock rates for a defined maturity via Bond Tokens (BTs). BTs trade at a discount before maturity on the fixed-rate AMM. The discount determines the implied rate.

> [Fixed-Rate Markets — Protocol](https://docs.fira.money/protocol/fixed-rate-markets.md)

### Floating-Rate Markets

Variable-rate borrowing and lending without maturity constraints. Rates adjust dynamically based on utilization — similar to existing DeFi lending protocols, but integrated into Fira's infrastructure.

> [Floating-Rate Markets — Protocol](https://docs.fira.money/protocol/floating-rate-markets.md)

### Dynamic Lending

LPs provide liquidity to the fixed-rate AMM while unused liquidity is rehypothecated to floating-rate vaults. LPs earn both trading fees and lending yield. Coupon Tokens (CTs) represent the yield portion and are tradable.

> [Rehypothecation](https://docs.fira.money/protocol/rehypothecation.md) · [Fixed-Rate Markets — Protocol](https://docs.fira.money/protocol/fixed-rate-markets.md) · [Floating-Rate Markets — Protocol](https://docs.fira.money/protocol/floating-rate-markets.md)

## Related

* [Architecture Overview](https://docs.fira.money/protocol/architecture-overview.md) — How markets connect to the broader system
* [Token Mechanics](https://docs.fira.money/protocol/token-mechanics.md) — BT, CT, and FW token mechanics
* [Risk Framework](https://docs.fira.money/security-and-risk/risk-framework.md) — How risk is assessed per market


---

# 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.fira.money/guides/overview.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.
