> 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/knowledge-score-api/01-overview.md).

# Overview

*"Measure. Score. Certify. Verify."*

This product has **no Lab, no lessons, and no exam of its own**. It reads results already produced by Crypto Readiness & Simulation and Compliance Training, and packages them into a score and a portable, verifiable credential. Endpoint-by-endpoint detail lives in the generated **API Reference** (tag: `Knowledge Score`), not on a separate page here.

### Products this API covers

| SKU          | What it unlocks                                      |
| ------------ | ---------------------------------------------------- |
| `SCR-VERIFY` | The score itself — free, generated automatically     |
| `SCR-CERT`   | PDF certificate + public verify link/QR              |
| `SCR-BANNER` | Shareable badge image                                |
| `SCR-SIG`    | Identity-verified signature on a certificate         |
| `SCR-REVAL`  | Refresh a decayed score without repurchasing a track |

### The full loop

```
1. Score is computed automatically   GET /me/score
                                       GET /me/score/{track}
                                       ← derived from Final Test results in the other two APIs

2. Score decays over time             GET /me/score/{track}  → decay_status: "stale"
                                        POST /me/score/{track}/revalidate

3. Package it as a credential         GET /certificates/{id}/download     (needs SCR-CERT)
                                        GET /badges/{id}/image              (needs SCR-BANNER)
                                        POST /certificates/{id}/signature   (needs SCR-SIG)

4. A third party checks it            GET /certificates/{id}/verify   ← public, no auth
                                        GET /scores/{id}/verify          ← public, no auth
```

### Why this is a separate product, not a feature of the other two

Keeping scoring and credentialing in one place means the same score/certificate shape works whether the underlying achievement came from a Readiness track or from Compliance Training. A third-party verifier (an exchange, an employer) only ever needs to know this one part of the API — it doesn't need to know or care which product produced the underlying 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/knowledge-score-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.