Introduction

LearnCoin is infrastructure for issuing verifiable credentials that anyone can verify without trusting LearnCoin. Every credential is a W3C Verifiable Credential 2.0 + Blockcerts v3 + Open Badges 3.0 document, cryptographically signed, Merkle-batched, and anchored on Ethereum L2 (Base). A recruiter, HR system, or AI agent can confirm authenticity using only the signed JSON-LD and the on-chain anchor — no LearnCoin API call required.

What you can do with LearnCoin

• Issue credentials through a REST API with per-tenant signing keys in HSM-protected GCP KMS
• Anchor every credential's Merkle root on Base (Ethereum L2) for public trust
• Verify any credential for free, forever, via a public URL that runs verification client-side
• Stay compliant — GDPR-aware schema keeps PII off-chain; erasure is supported by design

Who this documentation is for

• Issuers integrating LearnCoin as their credential layer (universities, training platforms, employers)
• Developers calling the REST API directly or via SDKs
• Verifiers building integrations that consume LearnCoin credentials
• Standards nerds who want the precise mapping to W3C VC 2.0, Blockcerts v3, and Open Badges 3.0

Where to go next

• Quickstart — get an API key and issue your first credential in under 10 minutes
• Core concepts — the vocabulary you'll need (credentials, batches, anchors, DIDs)
• Integration guides — common patterns: first integration, webhooks, GDPR erasure
• API reference — every endpoint with request / response shapes
• Standards — how LearnCoin implements W3C VC 2.0, Blockcerts v3, and Open Badges 3.0

Support

Questions, bug reports, or integration help: [email protected] — reply SLA is one business day, usually faster. For a quick scan of terminology before diving in, the public glossary has 101 definitions that each stand on their own URL.