> 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/readme.md). # What is LearnCard? [**LearnCard**](https://www.learncard.com) lets you issue digital credentials — badges, certificates, and achievements — that people own and share. Send one to any email address with [one API call](/start-here/your-first-integration.md); recipients claim it in the LearnCard app (or via a claim link). The resulting credential is a standard W3C Verifiable Credential (Open Badges 3.0) that other conformant wallets and verifiers can import and verify (see the [interoperability guide](/build/interoperate-with-learncard.md)). LearnCard is an open-source wallet, SDK, and network built on [W3C Verifiable Credentials](/understand/verifiable-credentials-vcs.md) and [Decentralized Identifiers (DIDs)](/understand/decentralized-identifiers-dids.md). The [Glossary](/start-here/glossary.md) defines these terms. Send a badge to your inbox (it asks for your email): ```bash npx @learncard/cli send ``` The [Quickstart](/start-here/your-first-integration.md) has code and no-key options. *** ### Why LearnCard? * **Portable**: Credentials travel with the learner, not locked into one system. * **Consent-Driven**: Learners control who sees their data, and when. * **Open**: Built on interoperable, community-driven standards. * **Developer-Friendly**: Integrates with existing apps through APIs and SDKs. *** ### What You Can Build LearnCard is used to: * Issue and verify credentials (skills, achievements, badges) * Build learner passports and skill profiles * Power AI copilots and bots that adapt to learner data * Create consent-based dashboards for families, schools, and career counselors * Support interoperability across educational, employment, and credentialing platforms *** ### Where to Go Next * **Send your first credential** → [Quickstart](/start-here/your-first-integration.md) * **Choose what to build** → [What Do You Want to Build?](/start-here/what-do-you-want-to-build.md) * **How LearnCard works** → [How LearnCard Works](/start-here/how-learncard-works.md) The sidebar has the full directory. *** LearnCard is open source and maintained by [**Learning Economy Foundation**](https://www.learningeconomy.io), a non-profit. ### Get Help * **Bugs and technical questions:** [Open an issue](https://github.com/learningeconomy/LearnCard/issues/new/choose). * **Want to contribute?** See [CONTRIBUTING.md](https://github.com/learningeconomy/LearnCard/blob/main/CONTRIBUTING.md) in the repo. * **Feature requests and releases:** [Request and vote on the roadmap](https://roadmap.learncard.com) and follow the [changelog](https://roadmap.learncard.com/changelog). * **Private or commercial questions:** Email or [contact Learning Economy](https://www.learningeconomy.io/contact). --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.learncard.com/start-here/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.