> For the complete documentation index, see [llms.txt](https://docs.yamato.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yamato.fi/en/features/health-rate-and-fee-rate.md).
# Health rate & Fee rate
One-time fee is charge at borrowing（borrowing amount \* fee rate）
Fee rate varies depend on health rate after borrowing.
Fees are subtracted at first hence user needs to purchase CJPY in order to fully repay debt.
Users can save fees by executing a borrowing at high health rate then withdraw collateral.
| Health Rate after borrowing(%) | Fee Rate(%) |
| :----------------------------: | :---------: |
| 130 | 4 |
| 150 | 2 |
| 200 | 1 |
| 250 | 0.85 |
| 300 | 0.7 |
| 350 | 0.55 |
| 400 | 0.4 |
| 500\~ | 0.1 |
The below graph shows the relationship between Fee Rate(Y-axis) & Health Rate(X-axis)
The collected fees are allocated to the redemption pool and the repayment pool at a ratio of Redemption Pool: Repayment Pool = 8:2.
---
# 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.yamato.fi/en/features/health-rate-and-fee-rate.md?ask=&goal=
```
`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.