# Meta Aggregator

## 1. Overview

The **Meta Aggregator** is a core feature of DackieSwap, designed to optimize token swaps by leveraging an **aggregator of aggregators** architecture. Instead of relying on a single liquidity source, it integrates with multiple leading aggregators to ensure users always receive the best possible execution.

When a user selects a swap pair, the system:

* Fetches quotes from multiple aggregators in parallel
* Selects the most optimal route based on many factors

***

## 2. How It Works

The Meta Aggregator queries multiple integrated aggregators simultaneously. Detail sequense as below:

<figure><img src="/files/MKcD0JVETU3IViQ8xerS" alt=""><figcaption></figcaption></figure>

1. User requests a swap\
   User selects tokens and amount → system starts searching for prices.
2. Check many providers at once\
   The platform quickly asks multiple aggregators (like Odos, Kyber, OKX, etc.) for quotes in parallel.
3. Show fastest result immediately\
   As soon as the first quote arrives, it is shown to the user → no waiting.
4. Improve results in the background\
   More quotes keep coming → system compares and may update to a better option.
5. Keep prices fresh automatically\
   If market changes, the system refreshes quotes in the background to stay accurate.
6. Execute the swap\
   User confirms → system sends the transaction using the best route selected.

{% hint style="info" %}
💡 Business value Better prices → compares multiple sources Faster experience → shows results instantly Higher success rate → avoids unreliable routes Always optimized → continuously improves in real time
{% endhint %}


---

# 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://docs.dackieswap.xyz/dackieswap/product-features/traders/meta-aggregator.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.