> For the complete documentation index, see [llms.txt](https://doc.ripcapsule.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ripcapsule.io/product/the-reveal.md).

# The reveal

When the card arrives, Capsule shows the back first. Large titles then appear one at a time: year, grade, then rarity. Each title settles into the caption under the card. The card then flips to the front.

On the $25 pack, Buyback and Double appear after the flip. On the Garage Pack the car is already sold. The screen shows the car and the buyback. It does not offer Double.

A title is skipped when that fact is missing. Capsule does not invent a year or a grade.

Insured value and the buyback quote appear with the result, after the flip. The buyback quote is the amount locked for that open. It is not a fixed percent of the pack price unless that is what the quote actually is.

Refreshing a card you have already revealed does not play the sequence again in that tab. A reduced-motion setting skips the motion and shows the front.

While the card is still loading, the screen keeps a dark slab. It does not show empty Year, Grade, or Rarity rows.


---

# 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://doc.ripcapsule.io/product/the-reveal.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.