These pages introduce the vocabulary you will see across the didx:me API: DIDs, verifiable credentials, SD-JWT and mDoc, selective disclosure, trust anchors. Each term maps to a specific decision you will make when you integrate: what a credential looks like, who can sign it, what the holder can withhold, and who gets to decide if a signature is trustworthy.Documentation Index
Fetch the complete documentation index at: https://docs.didx.co.za/llms.txt
Use this file to discover all available pages before exploring further.
What each page covers
Roles
Issuer, holder, verifier: who does what, and how information flows between them.
Credentials
DIDs, verifiable credentials, the two formats we support (SD-JWT VC and mDoc), and selective disclosure.
Templates and issuances
How credential templates, presets, and issuances relate to each other in the API.
Trust
How verifiers decide which issuers to accept. The part of the system that deserves the most attention on a real integration.
How the concepts map to the APIs
didx:me exposes three APIs. Each one is a different slice of the concepts above.| API | Role it serves | Concepts it covers |
|---|---|---|
| Consumer Onboarding | Bootstrap | User accounts, linking to an external identity provider if you have one |
Credentials (me-creds) | Issuer and verifier | Templates, presets, issuances, presentations, certificates, trusted entities |
Wallet (me-wallet) | Holder | Listing held credentials, approving presentations |