> For the complete documentation index, see [llms.txt](https://docs.learncard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.learncard.com/start-here/how-learncard-works.md).

# How LearnCard Works

The two-minute mental model — the integration flow, three layers, and one credential's journey.

LearnCard's mission is to help people collect, understand, and navigate their learning records, but the developer model is built around a simple flow: **Issuer → Credential → Holder → Verifier**.

## The Integration Flow

| Role         | What runs where      | Which API/SDK you call  |
| ------------ | -------------------- | ----------------------- |
| **Issuer**   | Your server (or CLI) | `send()` or `/api/send` |
| **Delivery** | LearnCard hosts      | Universal Inbox         |
| **Holder**   | Recipient's device   | Wallet app or SDK       |
| **Verifier** | Your server or app   | `verifyCredential()`    |

## Three layers

```mermaid
flowchart LR
  You["Your app · school · employer · game · AI agent"]
  subgraph LC["LearnCard — what people touch"]
    APP["LearnCard App · CLI"]
    SDK["Wallet SDK"]
  end
  subgraph CL["LearnCloud — open APIs"]
    NET["Network API<br/>send · share · verify · consent"]
    STR["Storage API<br/>encrypted personal data"]
    AI["AI API<br/>assess · analyze · tutor"]
  end
  STD["Open standards<br/>W3C Verifiable Credentials · DIDs · Open Badges 3.0 · CLR"]
  You --> LC
  LC <--> CL
  LC -.- STD
  CL -.- STD
```

* **LearnCard** is the wallet app and SDK. Signing and verification use a Rust core compiled to native and WebAssembly for web, iOS, Android, and Node.
* **LearnCloud** provides APIs for network delivery, user-controlled encrypted storage, and AI analysis. Each API can be used independently.
* **Open standards** support interoperability. LearnCard issues W3C Verifiable Credentials, usually Open Badges 3.0, that work with conformant wallets and verifiers. LearnCard also accepts credentials from other systems.

## One credential's journey

1. **You issue it.** Your seed (or a hosted signing authority you registered) signs a credential naming you as issuer. It's now tamper-evident: anyone can check the signature without asking you.
2. **You send it.** To a profile, a DID, or — for someone with no account — an email or phone via the **Universal Inbox**. They get a claim link.
3. **They hold it.** After claiming, the credential is stored encrypted in the person's own storage, under a **DID** they control. You can't revoke their copy of the *data* — only mark the credential's *status*.
4. **They share it.** With a verifier, an employer, another app — through **consent** the person grants and can withdraw. Verifiers check the signature and status; they don't need to call you.

The issuer's key signs the credential. Before claiming, an email recipient has no key and the credential waits in the inbox. After claiming, the holder's key controls storage and sharing. Verifiers need neither key.

## Where to go deeper

* Full architecture, including how a credential moves through every component → [Ecosystem Architecture](/understand/ecosystem-architecture.md)
* Why open standards are the point, not a feature → [Interoperability](/understand/ecosystem-architecture/interoperability.md)
* The credential formats themselves → [Verifiable Credentials](/understand/verifiable-credentials-vcs.md), [Boosts](/understand/verifiable-credentials-vcs/boost-credentials.md)
* Identity and keys → [DIDs](/understand/decentralized-identifiers-dids.md), [Storing your issuer seed](/build/go-to-production.md#security)
* Consent → [ConsentFlow Overview](/understand/consentflow-overview.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.learncard.com/start-here/how-learncard-works.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.