> 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/es/bridging/usdcx/bridge-app.md).
# Aplicación puente de USDCx
La aplicación USDCx Bridge es mantenida por Stacks Labs y funciona con Circle xReserve.
Adquiere USDCx a través de la [aplicación oficial de bridge](https://bridge.stacks.co/) o migra tu aeUSDC a USDCx para aprovechar una mejor liquidez y supuestos de confianza mejorados.
En el lanzamiento, el bridge USDCx en Stacks admite transferencias entre Ethereum y Stacks. El primer pool de liquidez aeUSDC–USDCx estará disponible en Bitflow a principios de enero.
El soporte para redes adicionales compatibles con Circle / CCTP está en la hoja de ruta y se implementará en el primer trimestre de 2026, lo que permitirá una mayor interoperabilidad en todo el ecosistema multichain de USDC de Circle.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.stacks.co/learn/es/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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.