# Technical Overview & API

## Technical Overview & API

Fluxion Network provides a decentralized exchange infrastructure built on automated market maker (AMM) hybrid with limit order architecture.

The protocol is compatible with Uniswap-style liquidity pools and includes both V2 and V3 style implementations.

This section documents the core contracts and APIs developers can interact with.

***

## Protocol Architecture

Fluxion AMM consists of the following components:

* Factory contracts — deploy and register liquidity pools
* Pool contracts — manage liquidity and swaps
* Router contracts — user entry point for swaps and liquidity
* Position manager — NFT-based liquidity positions (V3)
* Quoter — price quoting without executing swaps

About Fluxion limit order please view [this page](/fluxion-network/developer-resources/technical-overview-and-api/limit-order.md) 

***

## Contract Components

The protocol is organized into the following modules.

### AMM V2

* FactoryRegistry
* PoolFactory
* PoolImplementation
* PoolFees
* Router

These contracts implement the classic constant-product liquidity pool design.

### AMM V3

* Factory
* SwapRouter
* QuoterV2
* PositionManager
* WETH helper contract

These modules enable concentrated liquidity and advanced routing.

***

## Developer APIs

Developers typically interact with the following contracts:

| Component       | Purpose                    |
| --------------- | -------------------------- |
| Router          | Swap tokens                |
| Factory         | Create pools               |
| Quoter          | Simulate swaps             |
| PositionManager | Manage liquidity positions |

Detailed contract interfaces are documented in the pages below.


---

# 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://fluxion-network.gitbook.io/fluxion-network/developer-resources/technical-overview-and-api.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.