> For the complete documentation index, see [llms.txt](https://developer.portablewallet.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.portablewallet.net/crypto-readiness-and-simulation-api/01-overview.md).

# Overview

*"Learn. Simulate. Assess."*

Six tracks, each with its own catalog, lessons, testnet Lab, Simulator, and Final Test. This page explains the flow — the endpoint-by-endpoint detail for everything below lives in the generated **API Reference** (tags: `Readiness Catalog`, `Simulator`, `Final Test`, and each `* Lab`), not in a separate page per endpoint.

### Products this API covers

| SKU prefix | Track                   |
| ---------- | ----------------------- |
| `RDN-FUND` | Fundamentals            |
| `RDN-TRAD` | Trading                 |
| `RDN-MINE` | Mining & Infrastructure |
| `RDN-SEC`  | Security & Custody      |
| `RDN-DEFI` | DeFi                    |
| `RDN-NFT`  | NFTs                    |

Each sold as Starter ($39) / Pro ($179) / Expert ($349) — see the `Readiness Catalog` tag in the API Reference for what each tier unlocks.

### The full loop, per track

```
1. Catalog & Lessons   GET  /readiness/tracks/{track}/lessons
                        →  study the material

2. Simulator            POST /simulator/{track}/scenarios/{id}/start
                         →  practice the real Lab actions, unlimited, ungraded

3. Final Test            POST /final-test/{track}/start
                          →  graded lab session, limited attempts

4. Knowledge Score        GET  /me/score/{track}
                           GET /certificates → issued automatically on a pass
```

### Where each part of this lives in the API Reference

| Tag in the API Reference    | Covers                                                         |
| --------------------------- | -------------------------------------------------------------- |
| Readiness Catalog           | Track list, tiers, lesson content                              |
| Simulator                   | Practice sessions (shared shape across all 6 tracks)           |
| Final Test                  | Certification exam sessions (shared shape across all 6 tracks) |
| Fundamentals Lab            | Wallet backup, transfer, receive, fee estimation               |
| Trading Lab                 | Orders, order book, stop-loss, slippage                        |
| Mining & Infrastructure Lab | Nodes, block validation, staking                               |
| Security & Custody Lab      | Phishing detection, multisig, 2FA, approvals                   |
| DeFi Lab                    | Swaps, liquidity pools, contract interaction                   |
| NFT Lab                     | Minting, marketplace listing, royalties                        |

### What "certified" means

A track certificate is issued when a user passes that track's Final Test at Pro tier or above (≥80% score). Expert-tier certificates additionally require passing the advanced/edge-case checks. Certification and score packaging live in the separate **Knowledge Score** product — this one only produces the underlying pass/fail result.


---

# 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 dynamically by asking a question.

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

```
GET https://developer.portablewallet.net/crypto-readiness-and-simulation-api/01-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.