> For the complete documentation index, see [llms.txt](https://docs.term.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.term.finance/terminal-1-execution/integrations/erc4626.md).

# ERC4626

Terminal 1 supports ERC‑4626 vaults as a generic integration for sourcing funds from deployed capital. Where supported by a workflow, Terminal 1 can withdraw available assets from an ERC‑4626 vault and use those proceeds as inputs to a route (e.g., to fund an intent or satisfy a repayment leg), reducing the need to keep idle tokens in a wallet.

### What to expect

* Vault interactions appear as explicit steps in the route (withdraw/redeem as applicable).
* Available withdrawable amounts are determined at execution time and can change with vault conditions.
* If a vault cannot satisfy the requested withdrawal, the route will revert rather than partially complete.

### User considerations

* Vault liquidity and withdraw limits can change; previews may become stale.
* Some vaults impose delays, limits, or non-standard behavior; route support depends on workflow compatibility.
* Review the token that will be withdrawn and where proceeds will be routed next (swap, repayment, settlement).
* Ensure the vault share token is authorized where needed for withdrawal/redeem operations.