> For the complete documentation index, see [llms.txt](https://docs.oripa.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oripa.xyz/mechanics/melt-and-ship.md).

# Melt and ship

What you can do with a card you rip on oripa.xyz: melt it for USDC at 85% of its index price, or select it for shipping within 24 hours.

**TL;DR:** Any revealed card can be melted for USDC at 85% of its index price on the day of the melt, settled immediately. Each wallet can select up to 5 cards a day for shipping; a card not selected within 24 hours of its rip is melted automatically.

## Melt

Any revealed card can be melted for USDC at 85% of its index price on the day of the melt. Settlement is immediate.

* **When a card melts at its locked price.** If that day's index rests on fewer than 5 samples or fewer than 2 sources, the card melts at 85% of its locked price instead.
* **Ship or melt within 24 hours.** Each wallet can select up to 5 cards a day for shipping. A card not selected within 24 hours of its rip is melted automatically at that day's index, so any rise since the rip is included.
* **If the reserve falls short.** Melts are paid from the [reserve](https://docs.oripa.xyz/mechanics/reserve.md). While it covers every outstanding card, there is no limit on melts. On a day it does not, melts beyond what it covers wait and are paid in order once it does, at the price quoted when each melt was requested.

The melt rate (85% at launch) is a contract parameter and changes only through the 48-hour timelock. See [Contracts](https://docs.oripa.xyz/trust/contracts.md).

## Ship

Select a card for shipping within 24 hours of its rip, up to 5 cards per wallet per day. Regions, fees, carriers and timing: [Physical cards](https://docs.oripa.xyz/mechanics/physical-cards.md).

A melted card returns to inventory and can appear in a later pool at a new locked price. A shipped card leaves inventory.


---

# 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.oripa.xyz/mechanics/melt-and-ship.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.
