# Yield Aggreator(Stable Coins)

<figure><img src="https://3599231002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNQatX7C9EKgZqK2GRtcL%2Fuploads%2FJmZHjJq733zQPSP4UIZf%2Fyield%20banner%20copy.png?alt=media&#x26;token=8330fd07-4d13-44c3-a976-750743c81ade" alt=""><figcaption><p><strong>Yield Aggregator</strong></p></figcaption></figure>

**Yield Aggregator:**

With hundreds of yield farms popping up on the market daily, keeping track of the best-performing ones is tedious. If so, we can track a few, they are not accessible from a single point. To solve this problem, Polkstation has developed a Yield Aggregator to collate multiple best-performing farms in a single place. Polkastation hunts for yield optimization and secured farms in the market to help its community members maximize the yield.

Polkastation has four different farms:

USDT - USDT    :  30%  (Min Stake 30 Days)

BUSD - BUSD     : 10%  (Min Stake 20 Days)

DAI - DAI             :  8%    (Min Stake 15 Days)

USDC - USDC     :   5%  (Min Stake 15 Days)

On connecting the web 3 or injected wallet to Polkastation's farming page, you can stake, unstake, and harvest rewards with the click of a button. The farms offer an APR of 30% and the lock-in period is 15 days. The crypto assets added as liquidity to the farms cannot be withdrawn until the threshold locking period. But you can harvest the rewards daily. The Polkastation's farming UI comes with a robustly built and well-navigated dashboard that shows the users the amount of USDT earned.

**Visit :** [**https://polkastation.co/yield.html**](https://polkastation.co/yield.html)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://polkastation.gitbook.io/polkastation/important/yield-aggreator-stable-coins.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
