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

# Card inventory

How oripa.xyz pools are stocked: pools are built only from cards already in the vault, priced by the index, with every card list published before the first rip.

**TL;DR:** Pools are built only from cards already in the vault. Nothing is sold that is not on the shelf.

## Before a pool opens

* Every card in it is in the vault.
* Its index price is recorded as its locked price.
* The full card list, locked prices and sources are published on the pool page.
* The card list is committed onchain. See [Verify a pool yourself](https://docs.oripa.xyz/mechanics/verify.md).

## How pools are built

oripa.xyz builds every pool to an index RTP of 0.85. The theme of a pool and the cards in it are chosen by oripa.xyz. The order of the slots is not: it is shuffled from a block hash after the pool is committed (see [Verify a pool yourself](https://docs.oripa.xyz/mechanics/verify.md)).

## Restock

When a card is shipped, it leaves inventory. Each card's restock ratio, its restock cost over its locked price, is published on its pool page and capped by a contract parameter at 1.00. The part above 0.85 of the locked price is deducted from stakers' rip surplus, never from the user who ships. See [Rewards and staking](https://docs.oripa.xyz/token/rewards.md).

## What is never in a pool

* A card with no index price.
* A card that failed the intake check.

## Inventory figures

Live figures are listed on [Published figures](https://docs.oripa.xyz/trust/stats.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/card-inventory.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.
