> For the complete documentation index, see [llms.txt](https://docs.apyx.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apyx.fi/app-guide/how-to-buy-apxusd.md).

# How to Buy

General users can acquire apxUSD & aplUSD on the secondary market.

Using the Apyx Swap tab, general users can acquire apxUSD by swapping USDC through the Curve apxUSD/USDC:

1. Users initiate a purchase in the dApp interface by selecting USDC as the input asset.
2. The transaction is executed with MEV protection and routed via Li.Fi.
3. This flow allows users to swap USDC without interacting directly with the protocol’s minting or collateral mechanics. Small imbalances may emerge in the onchain AMM pool over time, creating incentives for whitelisted participants to rebalance the market through the mint and redemption workflows described below.

Additionally, over time, users will be able to acquire apxUSD across a wide range of DeFi, CeFi, and TradFi venues.

Minting apxUSD involves sending approved assets, like USDC, to the Apyx protocol in exchange for newly issued apxUSD. Redeeming involves burning to receive USDC. Redemption does not entitle the holder to the underlying preferred shares; the protocol liquidates collateral positions as needed to fund USDC redemption settlement.

Users interested in aptUSD can easily route from USDC through alqUSD to aptUSD via the Apyx swap tool in one seamless click.


---

# 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.apyx.fi/app-guide/how-to-buy-apxusd.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.