> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/adaptive-pools.md).

# Adaptive Pools

Integrate Peach’s dynamic-fee Uniswap v4 pools on Arc.

Peach Adaptive Pools use immutable Uniswap V4 Hooks to apply dynamic LP fees. Integrate pool discovery, quoting and settlement for crypto and RWA liquidity with the guides below.

### Get started

* [Overview](https://docs.peach.ag/documentation/arc/adaptive-pools/overview) — How the pools work, supported Hook types and Market SDK resources.
* [Quickstart](https://docs.peach.ag/documentation/arc/adaptive-pools/quickstart) — Install the SDK, initialize a client, discover pools, pin state, request quotes and prepare a first swap with router settlement.
* [Core Features](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features) — Trading fees, RWA calendars, Mid-block observations, liquidity, earnings, state reads and integration checks.
* [Contract Address](https://docs.peach.ag/documentation/arc/adaptive-pools/contract-address) — Arc Hook deployments, example PoolKeys, chain contracts and infrastructure.
* [Changelog](https://docs.peach.ag/documentation/arc/adaptive-pools/changelog) — Official SDK release notes, documentation versions and verification scope.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peach.ag/documentation/arc/adaptive-pools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
