> Source: [/docs/earn/vaults](https://tempo.xyz/developers/docs/earn/vaults.md) > Section: [Earn](https://tempo.xyz/developers/docs/earn.md). Choose a vault, deposit stablecoins, read positions, and withdraw. Earn is in beta; see the introduction for access. > [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md) > Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation. > If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly. # Vaults Choose a vault that accepts the stablecoin your customers hold and supports the access and withdrawal requirements of your product. ## Find a vault Use the vault address and network provided for your integration. Evaluate where its returns come from, what customers net, how they exit, and who can deposit. A vault's `verified` flag identifies a curated listing; it does not describe the strategy's risk or guarantee a return. ### Inspect a vault The demo starts with Sentora pathUSD on Tempo mainnet. Switch to Moderato testnet to inspect the pathUSD test vault. Each network lists only its approved demo vault, with live configuration from Tempo API. The interactive page defaults to Sentora pathUSD on Tempo mainnet and lets you switch to the pathUSD demo vault on Moderato testnet. The vault dropdown lists only the approved demo for the selected network. It reads that vault directly from Tempo API to show its asset, access rules, deposit status, withdrawal capabilities, and liquidity. See the [Earn API reference](https://tempo.xyz/developers/docs/api/earn) for request and response fields. Read your vault's configuration through the [Earn API reference](https://tempo.xyz/developers/docs/api/earn). Save its `id` (contract address) and network together. ## How vaults generate returns Each vault earns from one strategy. Strategies fall into three categories: * **U.S. Treasuries** — Tokenized U.S. Treasury bonds and sovereign debt products. * **Institutional credit** — Tokenized private credit, such as warehouse lending and CLOs. * **Collateralized lending** — Onchain lending pools. Rates move with borrow demand. An engine is the contract that connects an Earn vault to its underlying strategy. The vault directory reports each vault's engine and accepted asset; available strategies vary by network. | Source | How it connects to Earn | | --- | --- | | **Lending** | An engine deposits into an underlying lending vault. | | **Managed strategies** | An engine connects to a provider-managed vault that allocates funds across its strategy. | | **Tokenized assets** | An engine accesses an asset, such as tokenized treasuries or private credit, through a supported liquidity pool. | ## What changes a position's value A share's value moves with its strategy's returns, losses, and fees. A verified listing does not remove these risks. | Strategy | What moves value | | --- | --- | | **U.S. Treasuries** | Interest rates, and the tokenized product's issuer and redemption terms. | | **Institutional credit** | Borrower repayment. A default reduces value. | | **Collateralized lending** | Borrow demand sets the rate. A loan whose collateral falls short can cause a loss. | ## What customers net The observed `apy.vault` already reflects [Earn fees](https://tempo.xyz/developers/docs/earn/how-it-works#fees-and-revenue-share) and the underlying venue's fees. Show the remaining costs before the account deposits: | Cost | Where it appears | | --- | --- | | **Earn fees** | Already in the share price and `apy.vault`. `state.feesActive` reports whether the vault charges them. | | **Underlying venue fees** | Already in the engine's reported value. | | **Provider deposit, management, and withdrawal fees** | Read them from the provider before presenting a rate. | | **Network fees** | Each deposit and withdrawal transaction. | | **Moving funds from another network** | Each [Routes quote](https://tempo.xyz/developers/docs/routes/quotes), in and out. | | **Rewards** | Reported separately in the `apy` object, under temporary terms. | An observed APY describes a measurement window; it is not a promised return. ## How customers exit Check withdrawal support before the first deposit: | Path | Vault support | Settlement | When liquidity is short | | --- | --- | --- | --- | | **Immediate redemption** | `capabilities.redeem` | In the redemption transaction | Fails; it does not enter a queue. | | **Queued withdrawal** | `capabilities.asyncRedeem` | A request, then a later claim | Waits in the queue. | `instantLiquidity` describes vault-wide liquidity, not a user-specific quote; `null` means a reliable value is unavailable. [Withdraw](https://tempo.xyz/developers/docs/earn/withdraw) covers the exit flow. ## Who can deposit A vault accepts one stablecoin, and its share token is open or allowlisted to approved holders. Before enabling a deposit, check the accepted asset, the account's eligibility, `state.depositsPaused`, and the operations listed in `capabilities`. Use the deployed vault's supported operations through [Viem's Earn actions](https://tempo.xyz/developers/docs/earn/integrate). The Earn read API does not submit deposits or withdrawals. Continue with [Deposit](https://tempo.xyz/developers/docs/earn/integrate).