> 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/build.md). # Build - [Send & Issue Credentials](https://docs.learncard.com/build/send-credentials.md): One call sends a credential to an email, phone, or LearnCard profile. Sign it yourself or let LearnCard sign from a template. - [Revoke or Update a Credential](https://docs.learncard.com/build/send-credentials/revoke-or-update-a-credential.md) - [Issue & Refresh a Managed Credential](https://docs.learncard.com/build/send-credentials/issue-and-refresh-a-managed-credential.md): Issue a credential you can update later, publish the update, and pick it up in the recipient's wallet. - [Who Signs Your Credentials?](https://docs.learncard.com/build/send-credentials/create-signing-authority.md): Every credential is signed by a key. Decide whether you hold it or LearnCard holds one for you. - [Bootstrap an Issuer Organization](https://docs.learncard.com/build/send-credentials/bootstrap-an-issuer-org.md): Describe your organization in one file, apply it to staging, check it, then apply the same file to production. - [Know When a Credential Is Claimed](https://docs.learncard.com/build/send-credentials/listen-to-webhooks.md): Check whether a credential you sent was claimed — by asking, or by being told the moment it happens. - [Verify Credentials](https://docs.learncard.com/build/verify-credentials.md): Sign a credential locally, verify it, and understand tampered, expired, and revoked results. - [Build an App Inside LearnCard](https://docs.learncard.com/build/publish-your-app.md): Build, try, and publish an app that runs inside LearnCard and issues credentials to its users. - [Embed a Claim Button](https://docs.learncard.com/build/embed-a-claim-button.md): How-To Guide: Add a credential claim button to any website using the LearnCard Embed SDK - [Bring Your Credentials into LearnCard](https://docs.learncard.com/build/interoperate-with-learncard.md): Already issue credentials? Make LearnCard a place your users can claim them — with the protocol you use today, no new APIs required. - [Connect a User's LearnCard to Your Platform](https://docs.learncard.com/build/create-a-consentflow.md): Link a learner's LearnCard once, then read their data and issue to them automatically — with their permission. - [Record Learning Activity](https://docs.learncard.com/build/sending-xapi-statements.md): After a user connects their LearnCard, log what they do — and let them see it in their Activity Feed. - [Go to Production](https://docs.learncard.com/build/go-to-production.md) - [Generate API Tokens](https://docs.learncard.com/build/go-to-production/generate-api-tokens.md): Create a scoped token so your server can call the LearnCard API without holding a seed. - [Test Safely: Staging & Mock Recipients](https://docs.learncard.com/build/go-to-production/test-safely.md) - [Encrypt Hosted Signing-Authority Seeds](https://docs.learncard.com/build/go-to-production/signing-authority-seed-encryption.md) - [Get Listed as a Trusted Issuer](https://docs.learncard.com/build/go-to-production/verify-my-issuer.md): Add your organization's DID to the LEF Trusted Issuer Registry so recipients see a verified issuer. --- # 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/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.