> 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/developers/protocol-contracts/router.md).

# Router

The router is the single entry point for all user-facing protocol operations. It uses a diamond-like proxy pattern where each function selector maps to an action facet contract via `delegatecall`.

{% hint style="info" %}
Since all facets share storage via `delegatecall`, `RouterStorage` uses ERC-7201 storage namespacing to avoid collisions.
{% endhint %}

## FiraRouterV4

Extends OpenZeppelin's `Proxy` and overrides `_implementation()` to look up `CoreStorage.selectorToFacet[msg.sig]`. If no facet is registered, it reverts with `INVALID_SELECTOR`.

The constructor hard-wires the `setSelectorToFacets` and `selectorToFacet` selectors to the `ActionStorageV4` facet, allowing the owner to configure all other mappings post-deployment.

## Facet contracts

* [ActionBorrow](/developers/protocol-contracts/router/action-borrow.md) — Fixed-rate borrow and repay
* [ActionSwapBT](/developers/protocol-contracts/router/action-swap-bt.md) — BT swap operations
* [ActionSwapCT](/developers/protocol-contracts/router/action-swap-ct.md) — Synthesized CT swaps
* [ActionAddRemoveLiq](/developers/protocol-contracts/router/action-add-remove-liq.md) — Liquidity operations
* [ActionMisc](/developers/protocol-contracts/router/action-misc.md) — FW/BC minting, exits, multicall
* [ActionSimple](/developers/protocol-contracts/router/action-simple.md) — Gas-optimized on-chain approximation

## Shared base contracts

All facets inherit from `ActionBase`, which provides:

* FW mint/redeem orchestration
* BT/CT swap orchestration with limit order support
* Flash-callback encoding/decoding via `CallbackHelper`
* Delegation to `ActionSimple` when on-chain approximation suffices


---

# 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.fira.money/developers/protocol-contracts/router.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.