> For the complete documentation index, see [llms.txt](https://docs.aeralend.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeralend.app/how-it-works/lending-and-acook.md).

# Lending and aCOOK

What happens to COOK you lend, and what aCOOK is: a receipt whose redemption value rises rather than a balance that pays out. How the exchange rate moves.

In the COOK market, COOK is the only asset you can lend, and the only asset anyone can borrow. bCOOK is collateral and is never lent out to anybody — Aera will not do it — which is why bCOOK earns nothing here and keeps earning at BakeYourStake instead. On the Lend screen the bCOOK row says so: **Staking only** where a supply rate would be, **Not borrowable** where a borrow rate would be.

The COOK market is the only market. Aera's SOL market was retired on 22 October 2026 and now only redeems aSOL for SOL (see [Redeeming retired aSOL](/getting-started/redeem-asol.md)).

<figure><img src="https://3863521727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoMAgovgiKKIBsu11Xeij%2Fuploads%2Fgit-blob-7ea43b8e6b9b2410f64f36fd72c3de7d33c67af7%2Fmarket-row-cook.png?alt=media" alt="The COOK row opened: total supplied, available, supply cap, utilisation, collateral, limits and what one aCOOK redeems for"><figcaption><p>The COOK market, opened from its row on the Lend screen. <strong>1 aCOOK</strong> is what one aCOOK redeems for today. The balances are illustrative; the limits are the live ones.</p></figcaption></figure>

## aCOOK is your claim on the pool

When you lend COOK you receive **aCOOK**. It does not pay out; its redemption value rises.

The pool has a supply index that grows as borrowers pay interest. Your aCOOK balance never changes — what changes is how much COOK each unit redeems for. Lend 1,000 COOK, and when the index has risen 4.3% you redeem the same 1,000 aCOOK for 1,043 COOK. There is no claim step and no compounding decision.

That rate is the whole return, so the app shows it rather than leaving you to work it out: the market names aCOOK with what one redeems for today, the Lend sheet says how much aCOOK you will receive, and your balance card shows the aCOOK behind what you have lent — the balance your wallet and any explorer will call it.

The [aCOOK page](https://aeralend.app/acook/) shows the rate, the cash that redeems now, who holds it and who owes the market, all read from the chain, with the ways it can go wrong. It is explained in [aCOOK, the savings receipt](/how-it-works/acook-savings-receipt.md).

## What you can do with it

|                           |                                     |
| ------------------------- | ----------------------------------- |
| Redeem it for COOK        | Yes, subject to available liquidity |
| Hold or transfer it       | Yes — an ordinary SPL token         |
| **Post it as collateral** | **No.** The program refuses it.     |

The last one is deliberate. aCOOK is a claim on the same pool you would be borrowing from, so accepting it as collateral would let the pool collateralise loans against itself.

## Getting your COOK back

The limit is whatever is **available** in the pool. If borrowers have taken most of the liquidity you can withdraw only what is free, and you wait for repayments or for new lenders.

This is normal for a lending pool and it is not a fault — but it is a real risk, and worth understanding before lending an amount you may need back at short notice. The [interest curve](/how-it-works/interest-and-fees.md) is designed to resolve it quickly by making borrowing expensive as the pool empties.

{% hint style="info" %}
Locking bCOOK produces **abCOOK**, the matching receipt for collateral. You will see it named in transaction details. It is not something you need to hold, claim or manage.
{% endhint %}


---

# 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.aeralend.app/how-it-works/lending-and-acook.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.
