> 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/features/built-in-usdc.md).

# Built-in USDC

Use Built-in USDC to transfer USDC between supported networks within the app. You can also use USDC on one network to buy a token or fund an eligible DeFi position on another.

* **Transfer USDC across chains.** Choose an available USDC transfer route in the app. Routing is included, so you do not need to open a separate bridge interface.
* **Fund a swap or position.** On supported routes, your USDC is sent to the network used by the swap, pool, or vault. Funding a position from one chain does not mean the pool is on that chain. New stock LP positions in [Turbo Range](https://docs.degate.com/features/turbo-range.md) currently use Ondo stock/USDC pools on Ethereum. In [Power Pair](https://docs.degate.com/features/power-pair.md), choose **USDC Only** to fund a two-stock position with USDC. Check the funding network and the pool network before confirming.
* **Review costs before sending.** Supported USDC cross-chain transfers have no DeGate platform fee. Network fees still apply; review the quote and expected receipt before signing.

## FAQ

**Which networks can I move USDC between?** Check the USDC transfer screen for available source and destination networks. The [supported-network list](https://docs.degate.com/about-degate/readme.md#supported-networks) covers the wallet as a whole; a USDC transfer route may cover fewer networks.

**What does a cross-chain USDC transfer cost?** As of July 2026, supported same-asset USDC bridging is a 1:1 transfer with no DeGate platform fee. Network costs are separate. This does not set a 1:1 exchange rate between USDC and another asset. See [Fees](https://docs.degate.com/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/features/built-in-usdc.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.
