> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/developers/pool-vaults.md).

# Create your pool vaults

For a DEX: one partner vault for each token of your pool, created in one step from your curator wallet or your Safe, and shown as one card.

A DEX that lends its pool's tokens through gage keeps one partner vault for each pool token gage lends. A partner vault lends one asset, so an NVDA/USDG pool has two: a USDG vault and an NVDA vault. You create both in one step, and Earn shows them as one card with two sides.

## Before you start

* **Your curator.** One address manages both vaults, for good: the wallet or Safe that creates them. Since 5 November 2026 any address can create them, on gage.cash or with gage-sdk (below).
* **Your pool's tokens.** gage lends USDG, GLD, NVDA, HIMS and frxUSD, so a frxUSD/USDG pool gets both vaults. A token gage does not lend, such as WETH in a WETH/USDG pool, gets no vault: only the other one is created.
* **What lenders take on.** Each vault lends its own token at a fixed cost, against the collateral you choose. A loan is never closed early because a price moves; if a borrower does not repay by the end of the term, the vault keeps the collateral. Its depositors may end up holding the collateral instead of the token they deposited.

## On gage.cash

1. Open [Create a vault](https://gage.cash/earn/create) with your curator connected, and at the first step, **Deposits**, choose **LP pair**. For a Safe as curator, choose **A Safe** at the **Manager** step.
2. **Pair.** Name your vaults, for example `Fables`, and pick your pair's two tokens: the token, then what it is paired with. Both vaults carry one name, ending in the pair: `Fables NVDA/USDG`.
3. **Manager.** **This wallet**, or **A Safe** and its address. The page says on which tokens' vaults the manager is a partner.
4. **Collateral.** Choose what each vault lends against. A stock's vault lends against the tokens gage pairs with it. The USDG vault starts on the collateral type of your pool's other token. Neither vault starts on your pool's own two tokens, so a fall in one of them does not hit your pool twice; you can still pick one.
5. **Limits.** For each vault, its largest loan in its own token and its **Cash kept free**: the share it keeps free, in cash or in its reserve, which your pool can draw on and which pays withdrawals at once (10% to start, 0% to 100%). The longest loan and the lowest Loan grade apply to both.
6. **Fees.** One performance fee and one priority fee for both.
7. **Loans.** Which loans the vaults take: **New loans**, or **New and existing**, where each vault also buys running loans that other vaults of its token sell, for less than they repay. You set the least a bought loan must earn: an extra return a year above the model's rate.
8. **Review**, then:
   * From a wallet: **Create both vaults**. A wallet that signs a batch of calls (EIP-5792) signs once; any other wallet signs each vault in turn.
   * From a Safe: **Download Safe batch**. In Safe{Wallet}, open Apps, then Transaction Builder, and drop the file in. Check each call, then sign and execute with your Safe's owners. The vaults appear on Earn once it runs.

## What links the two vaults

Nothing on chain. Both vaults carry one name that ends in your pool's tag, its two tokens' symbols joined by a slash, and they share their curator. gage reads a vault as one side of a pool when its name ends in a tag naming the asset it lends. If you rename one of them, it leaves the pool, so keep both names alike.

`GET /intent/partners/pools?curator=<your curator>` on gage's indexer lists your pools, each side with its vault, or none (see [API](https://docs.gage.cash/developers/api.md)).

## From code

[gage-sdk](https://docs.gage.cash/ai-agents/sdk.md)'s `createPoolVaults` returns the same calls, each simulated from your curator: `calls` for one wallet batch (`wallet_sendCalls`), and `safeBatch`, the Safe{Wallet} Transaction Builder file. `poolVaults({ curator })` finds your pools. [gage-mcp](https://docs.gage.cash/ai-agents/mcp.md) serves both as tools, `gage_create_pool_vaults` and `gage_pool_vaults`. Neither signs.

```ts
import { createGage } from "gage-sdk";

const gage = createGage();
const made = await gage.createPoolVaults({
  curator: "0xYourSafe",
  name: "Fables",
  pool: ["NVDA", "USDG"],
  term: 604_800, // the longest loan: 7 days
  feeBps: 1_000, // a 10% performance fee
  sides: [
    { token: "NVDA", maxLoan: "5000000000000000000" }, // at most 5 NVDA in one loan
    { token: "USDG", maxLoan: "1500000000", cashKeptFreeBps: 1_000 }, // at most 1,500 USDG, 10% kept free
  ],
});
// made.calls: one wallet batch from the curator. made.safeBatch: the file a Safe's owners load and sign.
```


---

# 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.gage.cash/developers/pool-vaults.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.
