> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/dex/migration/v1.md).

# DEX v1 integration

STON.fi DEX v1 SDK documentation - integrate swaps, liquidity provision, and LP token management

The remaining sections of the documentation will demonstrate specific examples of the DEX usage:

* [methods reference](/developer-section/dex/migration/v1/reference.md)
* [perform a swap operation](/developer-section/dex/migration/v1/swap.md)
* [provide liquidity](/developer-section/dex/migration/v1/provide-liquidity.md)
* [refund liquidity](/developer-section/dex/migration/v1/refund-liquidity.md)
* [burn liquidity tokens](/developer-section/dex/migration/v1/burn-lp-tokens.md)

## Version and fee scope

This section targets deployed DEX v1 contracts, not npm SDK major version 1. Use the installed SDK wrappers that match those contracts. [DEX v1 direct payouts](/developer-section/dex/fees.md#dex-v1-direct-payouts) do not use v2 Vaults or their accrual/withdrawal datasets. For current v2 operations, use [SDK integration](/developer-section/dex/sdk.md); for version selection, use [Versions and migrations](/developer-section/dex/migration.md).


---

# 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.ston.fi/developer-section/dex/migration/v1.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.