> 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/aggregator/core-features.md).

# Core Features

Use the Arc Aggregator SDK to quote, execute and manage swaps.

Start with [Quickstart](https://docs.peach.ag/documentation/arc/aggregator/quickstart) to install and create a client. Configure the client first, then learn quotes, slippage and fees. Choose an execution mode after these shared concepts.

| Feature                                                                                                                            | What you can do                                                 |
| ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| [Client Configuration](https://docs.peach.ag/documentation/arc/aggregator/core-features/api-configuration-cancellation-and-errors) | Configure the SDK client, request lifecycles and error handling |
| [Quotes and Routing](https://docs.peach.ag/documentation/arc/aggregator/core-features/quotes-and-routing)                          | Read quote amounts, select providers and confirm returned terms |
| [Slippage](https://docs.peach.ag/documentation/arc/aggregator/core-features/slippage)                                              | Set tolerance and protect the confirmed minimum net output      |
| [Fees](https://docs.peach.ag/documentation/arc/aggregator/core-features/custom-fee-and-slippage)                                   | Configure custom fees and explain their allocation              |
| [Transaction Safety](https://docs.peach.ag/documentation/arc/aggregator/core-features/validation-approvals-and-expiry)             | Check approvals, prepared results, deadlines and receipts       |
| [Direct Swaps](https://docs.peach.ag/documentation/arc/aggregator/core-features/direct-allowance)                                  | Execute from the token owner’s wallet                           |
| [Delegated Swaps](https://docs.peach.ag/documentation/arc/aggregator/core-features/delegated-execution-with-permit2-witness)       | Execute with separate payer and executor accounts               |

The Direct flow is `swap` → review and confirm its quote and transaction → approve if needed → wallet submission. One `swap` call gets both quote and transaction; submission reuses that result. Delegated swaps use prepare → review and confirm → payer signature → build. Neither preparation nor build broadcasts a transaction.

For Launchpad tokens, see [Trading before and after graduation](https://docs.peach.ag/documentation/arc/launchpad/core-features/trading-before-and-after-graduation). Raw endpoints and HTTP response fields are documented separately in [API Reference](https://docs.peach.ag/api-reference/arc-aggregator).


---

# 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/aggregator/core-features.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.