> For the complete documentation index, see [llms.txt](https://docs.degate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.degate.com/getting-started/your-first-swap.md).

# Your First Swap

A swap on DeGate works the same whether the token lives on the chain your funds are on or a different one: you choose the token, DeGate handles routing, bridging, and gas behind the scenes, and the result lands in your unified balance.

## Before you start

Buys on DeGate are paid in USDC, and selling a token settles back into USDC. So you need USDC first, and there are two ways to get it: deposit USDC from any supported chain, or sell a token you already hold (for example, selling TSLAx gives you USDC to buy with; note that a sell still needs network fees covered, so it may not go through if your wallet holds nothing besides that token). There is no need to hold the destination chain's gas token. See [Quickstart](/getting-started/quickstart.md) if you have not set up yet.

## Steps

1. Open **Swap** in the app.
2. Search for the token you want to receive. You can search across all supported chains at once.
3. Pay with USDC from your balance.
4. Review the quote. The app shows the expected output amount and price impact before you confirm, and the displayed amount reflects the DeGate swap fee for that token tier (see [Fees](/fees/fees.md)).
5. Confirm. Same-chain swaps complete in seconds; cross-chain swaps typically take 30 seconds to 2 minutes, and the app shows an estimated completion time before you confirm. You can follow progress in the **Activity** tab.

If market conditions change significantly during execution, the transaction reverts and your original tokens are returned automatically.

## What happens in the background

DeGate finds the route, executes any bridging, and pays gas on the chains involved by purchasing the necessary gas tokens automatically. You sign with your own key; at no point does DeGate take custody of your assets. The mechanics are described in [Cross-chain Swap](/features/cross-chain-swap.md).

## FAQ

**Why is my swap taking longer than expected?** Cross-chain routes settle on more than one network and inherit those networks' confirmation times; congestion can add delay. Check the Activity tab, and see the [FAQ](/support/faq.md) if a swap seems stuck.

**Is there a limit on how much I can swap?** There are no account-based limits. For very large swaps, price impact may be higher on assets with lower on-chain liquidity; the app displays price impact before confirmation.

**What fee did I pay?** Swap fees have two tiers, set by the token traded against USDC: 0% for stablecoins, and 0.02% for all other tokens, as of August 2026. Details: [Fees](/fees/fees.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.degate.com/getting-started/your-first-swap.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.