> For the complete documentation index, see [llms.txt](https://paragon-protocol.gitbook.io/paragon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paragon-protocol.gitbook.io/paragon-protocol/core-products/paragon-swap/overview.md).

# Overview

### Launch Liquidity Model

At launch, Paragon uses **aggregated liquidity via 1inch**.

This allows:

* immediate access to deep liquidity
* reliable pricing from day one
* routing across multiple external venues

As Paragon evolves, native liquidity pools will be integrated alongside aggregation to create a hybrid execution system.

***

### What Makes Paragon Different

Most DEXs:

* execute instantly
* expose trades to the public mempool
* return the available price

Paragon:

* protects execution
* optimizes routing
* improves trade outcomes

***

### Two Execution Modes

#### 1. Classic Swap

* instant execution
* standard routing
* simple and fast

👉 Best for:

* small trades
* quick execution

***

#### 2. Flow Swap (Recommended)

* intent-based execution
* solver competition
* batch settlement

👉 Best for:

* optimal pricing
* reduced MEV exposure
* improved execution quality

***

### Built on Paragon Shield

All swaps benefit from Paragon Shield:

* private transaction routing
* reduced sandwich risk
* execution validation

***

### Aggregated Liquidity

Paragon routes trades across:

* external liquidity (via 1inch)
* Paragon pools (as they are introduced)
* multi-hop optimized paths

👉 Result:

* deeper liquidity access
* more efficient routing
* improved pricing

***

### Execution Outcomes

Paragon enforces:

* minimum output protection (minOut)
* execution validation before settlement
* fallback or revert if conditions are not met

👉 Any execution improvements are handled through the Surplus & Rebates system.

***

### How a Swap Works

1. Enter trade details
2. Choose execution mode
3. Confirm in wallet

Behind the scenes:

* trade is routed privately
* liquidity is aggregated
* execution is validated

***

### What You See

After execution:

* final output
* execution route
* any improvement vs expected outcome

👉 Displayed as:

**“You saved X%”**

***

### Who It’s For

**Traders**

* better pricing
* improved execution
* protected trades

***

**Liquidity Providers**

* trading fees (from pools)
* participation in execution routing

***

**Long-Term Participants**

* governance access
* exposure to protocol growth

***

### ⚠️ Important Notes

* trades respect your minimum output
* trades may revert if conditions change
* fallback options may be available

***

### Summary

Paragon Swap delivers:

* optimized execution
* reduced MEV exposure
* aggregated liquidity access
* improved trade outcomes

Paragon Swap is not just a DEX interface.\
It is the entry point into a system designed to make trading more efficient, protected, and transparent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://paragon-protocol.gitbook.io/paragon-protocol/core-products/paragon-swap/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.