<!-- tempo-docs-context -->
> Source: [/docs/earn/providers](https://tempo.com/developers/docs/earn/providers.md)
> Section: [Earn](https://tempo.com/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.com/developers/llms.txt) · [Docs skill](https://tempo.com/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.com/developers/llms.txt) and Markdown pages directly.

# Connect a strategy

<span id="connect-a-yield-source" />

An engine connects an Earn vault to its underlying yield strategy. If you operate a lending market, managed strategy, or liquidity pool, agree the engine interface and deployment with Tempo before integrating it.

## Define the vault

Specify the accepted stablecoin, strategy, share valuation, venue and [Earn fees](https://tempo.com/developers/docs/earn/how-it-works#fees-and-revenue-share), and account eligibility. Applications show these terms to customers. The [vault configuration](https://tempo.com/developers/docs/earn/vaults) exposes the asset, engine, access rules, and supported capabilities.

## Define deposits and withdrawals

Document the contract interface and approvals required to deposit, and how the vault issues shares. Define whether redemptions are immediate or queued, the liquidity available to serve them, and how applications track completion.

Applications use [Viem’s Earn actions](https://tempo.com/developers/docs/earn/integrate) for supported vault operations and the [Earn API](https://tempo.com/developers/docs/api/earn) for discovery, positions, share prices, and earnings. Document any engine-specific restrictions or queued withdrawal requirements.

## Confirm the integration

[Contact Tempo](https://tempo.com/contact) to agree the engine interface, deployment, and supported operations. Mention any planned Zone integration, since it adds routing, access, and tracking requirements.

See [How Earn works](https://tempo.com/developers/docs/earn/how-it-works) for the shared vault model and [Deposit](https://tempo.com/developers/docs/earn/integrate) for the application flow.
