> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/learn/zh/bridging/usdcx/bridge-app.md).
# USDCx Bridge 应用
USDCx Bridge 应用由 Stacks Labs 维护，并由 Circle xReserve 提供支持。
通过以下方式获取 USDCx [官方桥接应用](https://bridge.stacks.co/) 或者将你的 aeUSDC 迁移到 USDCx，以享受更好的流动性和更优的信任假设。
在上线时，Stacks 上的 USDCx 桥支持以太坊和 Stacks 之间的转账。首个 aeUSDC–USDCx 流动性池将于一月初在 Bitflow 上线。
对更多兼容 Circle / CCTP 的网络的支持已列入路线图，并将于 2026 年第一季度推出，从而在 Circle 的多链 USDC 生态系统中实现更广泛的互操作性。
---
# 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.stacks.co/learn/zh/bridging/usdcx/bridge-app.md?ask=&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.
