> 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/what-do-you-want-to-build.md). # What Do You Want to Build? Pick your path — every integration starts with one of these six jobs. Most LearnCard integrations fit one of six paths. Each starts with the lowest-effort method. ## 🎖️ Send & issue credentials Issue badges, certificates, or credentials by email, phone, or LearnCard profile. Examples include universities issuing diplomas, bootcamps certifying skills, and employers recognizing training. * **No code**: issue directly from the [LearnCard app](https://learncard.app) * **One API call**: [send a credential to an email](/start-here/your-first-integration.md) (\~15 lines) * **At scale**: [issue at scale with templates](/build/send-credentials.md#issue-at-scale-with-templates) * **Templates, webhooks, and guardian consent**: [all sending patterns](/build/send-credentials.md) * **OID4VCI, VC-API, or signed JSON**: [bring existing credentials into LearnCard](/build/interoperate-with-learncard.md) ## 📱 Publish your app in LearnCard Put your product inside the LearnCard app store, where users can install and launch it. Your app gets single sign-on, credential issuance, notifications, and learner context via the Partner Connect SDK. Examples include AI tutors using consented learner history, games issuing portable badges, and career tools building skills profiles. * Start here: [Build an App Inside LearnCard](/build/publish-your-app.md) — local mock mode to published listing * Full API surface: [Partner Connect SDK](/reference/partner-connect.md) ## 🌐 Add LearnCard to your site Let users claim credentials from your website or app — from a one-script claim button to a full embedded experience. Examples include an LMS awarding course completions and a conference site offering an attendance badge. * **One script tag**: [embed a claim button](/build/embed-a-claim-button.md) * **Connected accounts**: [Connect a User's LearnCard to Your Platform](/build/create-a-consentflow.md) — users link once, you issue automatically * **All options**: [Connect a User's LearnCard to Your Platform](/build/create-a-consentflow.md) ## 🤝 Manage consent & guardianship Request user consent to read or write data, with built-in guardian approval flows for minors. Examples include parent-approved school apps and scouting organizations issuing to minors with guardian consent. * Start here: [Create a ConsentFlow](/build/create-a-consentflow.md) * Concepts: [ConsentFlow overview](/understand/consentflow-overview.md) ## 🔬 Going deeper First decide [who signs](/build/send-credentials/create-signing-authority.md): **you** (keep a seed on your server; the SDK authenticates with your DID) or **LearnCard** (a hosted signing authority plus an API token from the Developer Portal or `addAuthGrant`). Verification-only code needs neither. * [Generate API tokens](/build/go-to-production/generate-api-tokens.md) * [Test safely on staging](/build/go-to-production/test-safely.md) * [Go to Production](/build/go-to-production.md) * [Build a Plugin (GitHub)](https://github.com/learningeconomy/LearnCard/blob/main/packages/learn-card-core/PLUGINS.md) ## ✅ Verify credentials Check badges, degrees, and certificates presented to your hiring or verification service. * Start here: [Verify Credentials](/build/verify-credentials.md) — sign locally, then test valid, tampered, expired, and revoked outcomes * Decide which issuers to accept with [Trust Registries](/understand/decentralized-identifiers-dids/trust-registries.md); a valid signature alone is not issuer trust. *** For help choosing a path, [open an issue](https://github.com/learningeconomy/LearnCard/issues/new/choose) or email . --- # 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/what-do-you-want-to-build.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 `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.