# How Numex Works

Numex should feel like a premium coin marketplace, not a crypto app. The collector sees curated packs, certified coins, portfolio holdings, integrity proofs, and redemption options. Blockchain infrastructure stays behind the scenes.

```mermaid
flowchart LR
  A["Browse cinematic vault marketplace"] --> B["Inspect packs and certified coins"]
  B --> C["Buy pack with USDC (Apple Pay / card / wallet)"]
  C --> D["Open reveal experience"]
  D --> E["Receive certified coin"]
  E --> F["View portfolio holding"]
  F --> G["Review integrity proof"]
  F --> H["Request physical redemption"]
```

## Two Acquisition Paths

```mermaid
flowchart TD
  A["Browse marketplace"] --> B{"Acquisition type"}
  B -->|"Direct purchase"| C["Buy unowned coin at ask price"]
  B -->|"Pack purchase"| D["Buy pack → reveal → receive coin"]
  C --> E["Coin assigned to portfolio"]
  D --> E
  E --> F["Integrity proof generated"]
  F --> G["Chain anchor queued"]
```

* **Marketplace purchase:** Unowned coins display a deterministic ask price within +/-10% of estimated market value. Purchasing assigns ownership.
* **Pack reveal:** Pack purchase triggers the reveal engine, which selects a coin from the committed pool. The revealed coin is assigned to the buyer.

## User Promise

* Clear pack pricing and odds.
* Real coin data and stored media.
* Marketplace ask prices for unowned coins.
* 90% vault bid for owned coins.
* Premium reveal experience.
* Vaulted ownership record.
* Redemption path for physical delivery.
* Integrity proof that connects the portfolio coin to a physical vaulted asset.
* One physical coin, one owner. No double ownership.

## What We Avoid In Buyer UX

* Wallet-first onboarding.
* Gas language.
* Chain jargon as the primary trust story.
* Claims that a coin is registry-backed before chain reconciliation is complete.
* Calling commitment-based proofs "zero-knowledge" (they are verifiable commitments).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://numex-greenfield.gitbook.io/numex-docs/getting-started/collector-experience.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.