> 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/valuation.md).

# How cards are valued

How oripa.xyz prices a card: a weighted median of completed sales, C2C listings and shop prices, converted from yen once a day and published with its sources.

**TL;DR:** Every card's index price is a weighted median of its recent market prices: completed sales count three times, C2C listings twice and shop prices once. It updates once a day, and every card's price, sources and update time are public.

The index is the price the platform owes: every melt is paid at it, every reserve is held at it, and every locked price is taken from it when a pool is built.

## Sources

Each marketplace or shop is one source and gives one value:

| Source type                                                          | Value used                                                                    | Weight                                                    |
| -------------------------------------------------------------------- | ----------------------------------------------------------------------------- | --------------------------------------------------------- |
| **Completed sales** (Mercari, Yahoo! Auctions, SNKRDUNK and others)  | Median of the last 14 days, weighted toward recent sales (half-life 3.5 days) | 3; a source with fewer than 2 sales counts at half weight |
| **C2C marketplace listings**                                         | Median of the 7 lowest listings in the last 7 days                            | 2                                                         |
| **Retail shops** (Hareruya, Yuyu-tei, Surugaya, Card Rush, Torecolo) | Lowest in-stock price in the last 7 days                                      | 1                                                         |

With three or more sources, a source more than 40% away from the median is left out. Buy-list prices are not used. Graded cards are priced separately by card, grading company and grade.

## Currency

Index prices are in yen. Once a day they are converted to USDC at that day's USD/JPY rate from ExchangeRate-API (open.er-api.com), fetched at 20:00 UTC and published with the day's index at 23:40 UTC. Every melt that day and every pool built that day use that one rate.

## Update

Once a day. Each card's price, its sources, its update time and the method version of the index are public. Changes to the method are listed on [Changelog](https://docs.oripa.xyz/trust/changelog.md).

## Locked price and melt price

* **Locked price.** When a pool is built, each card's index price at that moment is recorded as its locked price. It is fixed while the pool is live and sets the pool's RTP, each rip's recorded loss and the reserve set aside for the card.
* **Melt price.** 85% of the card's index price on the day of the melt. A later change in the index changes what a card melts for, never the loss a rip recorded.

When a day's index for a card rests on too few samples or sources, the card melts at 85% of its locked price instead. See [Melt and ship](https://docs.oripa.xyz/mechanics/melt-and-ship.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.oripa.xyz/mechanics/valuation.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.
