walt.id valid
walt.id Documentation
walt.id provides digital identity and wallet infrastructure: decentralized identifiers (DIDs), verifiable credentials (W3C VC, IETF SD-JWT VC, ISO mDL/mdoc), and the OID4VC exchange protocols (OID4VCI, OID4VP). There are TWO DISTINCT product lines — do not mix them up: the **Community Stack** (free, open source: Issuer API, Verifier API, Wallet API, libraries) and the **Enterprise Stack** (commercial: multi-tenant platform with organizations/tenants/services, admin APIs, KMS/IAM integrations). T
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T23:37:01.799Z. Cached copy · Source on walt.id
# walt.id Documentation
> walt.id provides digital identity and wallet infrastructure: decentralized identifiers (DIDs), verifiable credentials (W3C VC, IETF SD-JWT VC, ISO mDL/mdoc), and the OID4VC exchange protocols (OID4VCI, OID4VP). There are TWO DISTINCT product lines — do not mix them up: the **Community Stack** (free, open source: Issuer API, Verifier API, Wallet API, libraries) and the **Enterprise Stack** (commercial: multi-tenant platform with organizations/tenants/services, admin APIs, KMS/IAM integrations). Their APIs and base paths differ; always check which stack a page belongs to.
Stack versions: Community Stack 1.2.0, Enterprise Stack 1.2.0. Index generated 2026-10-19.
How to use these docs as an AI agent:
- Every page below links to its raw markdown version (append `.md` to any docs.walt.id page URL). Each raw page carries frontmatter stating its stack, version, and canonical URL.
- [Community Stack vs. Enterprise Stack](https://docs.walt.id/community-vs-enterprise.md): Read this first to pick the right stack.
- [walt.id company and product facts](https://walt.id/facts.md): Canonical reference for what walt.id is, its editions, licensing, components and supported standards. Use it when describing walt.id; it takes precedence over older blog posts and white papers.
## Full-Text Bundles
- [llms-full.txt](https://docs.walt.id/llms-full.txt): Entire documentation (Concepts + both stacks) in a single file, with explicit PART separators between Community and Enterprise content
- [llms-community-stack.txt](https://docs.walt.id/llms-community-stack.txt): Concepts + Community Stack only — use this when working with the open-source Issuer/Verifier/Wallet APIs
- [llms-enterprise-stack.txt](https://docs.walt.id/llms-enterprise-stack.txt): Concepts + Enterprise Stack only — use this when working with the commercial multi-tenant platform
## API Specifications (machine-readable, OpenAPI 3.1)
- [Issuer API — Community Stack](https://issuer.demo.walt.id/api.json): OpenAPI 3.1 spec for the walt.id Community Stack open-source Issuer API ([Swagger UI](https://issuer.demo.walt.id/swagger/index.html))
- [Verifier API — Community Stack](https://verifier.demo.walt.id/api.json): OpenAPI 3.1 spec for the walt.id Community Stack open-source Verifier API ([Swagger UI](https://verifier.demo.walt.id/swagger/index.html))
- [Wallet API — Community Stack](https://wallet.demo.walt.id/api.json): OpenAPI 3.1 spec for the walt.id Community Stack open-source Wallet API ([Swagger UI](https://wallet.demo.walt.id/swagger/index.html))
- [Enterprise API — Enterprise Stack](https://enterprise.sandbox.walt.id/api.json): OpenAPI 3.1 spec for the walt.id Enterprise Stack API ([Swagger UI](https://enterprise.sandbox.walt.id/swagger/index.html))
## Concepts
- [Concepts](https://docs.walt.id/concepts.md): Learn more about the general building blocks of decentralized ID solutions.
- [Decentralized Identity](https://docs.walt.id/concepts/decentralized-identity.md): An in
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| certifier.io | Certifier | interface Business software AI agents and MCP +1 | US | 52 | ✓ | ||
| hexclave.com | Hexclave | interface Open source projects Developer tools +1 | US | 54 | ✓ | ✓ | |
| pingidentity.com | Ping Identity | documentation Cybersecurity Authentication and identity | US | 66 | ✓ | ✓ | |
| stytch.com | Stytch | interface Authentication and identity APIs and SDKs | — | 55 | ✓ | ✓ | |
| validationcloud.io | Validation Cloud | interface Infrastructure APIs and SDKs +1 | US | 49 | ✓ | ||
| icommunity.io | iCommunity | documentation Infrastructure Cybersecurity | PL | 46 | ✓ | ||
| workos.com | WorkOS Documentation | interface Cybersecurity Authentication and identity +1 | US | 66 | ✓ | ✓ | |
| signicat.com | Signicat | documentation Cybersecurity Authentication and identity | — | 61 | ✓ |
Machine-readable: GET /v1/resolve?q=walt.id · GET /v1/domain/walt.id · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage walt.id, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for walt.id:
1. POST https://agentwebmap.com/v1/sites/walt.id/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://walt.id/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/walt.id/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/walt.id).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.