> 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/apps/apps.md).

# Apps Overview

LearnCard powers several user-facing applications. This section documents how users interact with these apps and the key flows they enable.

## Available Apps

### [LearnCard App](/apps/learn-card-app.md)

The flagship mobile and web wallet for managing verifiable credentials. Users can:

* Claim credentials via links or QR codes
* Store and organize badges, achievements, and IDs
* Share credentials with verifiers
* Connect with other profiles on the LearnCard Network

### [ScoutPass](/apps/scouts.md)

A specialized app for scouting organizations to issue and manage achievement badges. Features:

* NSO → Troop → Scout hierarchy using Boost parent-child relationships
* BoostID membership cards at each level
* Role-based permissions for badge issuance
* Digital badges for ranks, skills, and achievements

***

## For Developers

If you're building integrations with these apps, see:

* [Connect a Website](/how-to-guides/connect-systems/connect-a-website.md)
* [LearnCard Network API](/sdks/learncard-network.md)
* [ConsentFlow Overview](/core-concepts/consent-and-permissions/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 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://docs.learncard.com/apps/apps.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.