> For the complete documentation index, see [llms.txt](https://docs.toolkit.equs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolkit.equs.ai/docs/about-the-system/standards.md).
# Supported Standards
The open standards EQUS Developer Toolkit supports, with versions: OID4VCI, OID4VP, DCQL, SD-JWT VC, Token Status List, mDoc, W3C VCs and DID methods.
### Protocol stack
EQUS Developer Toolkit builds on open Decentralized Identity standards so you can run **Issuer** and **Verifier** journeys that interoperate with standards-based wallets and credential ecosystems.
This page lists the standards and profiles relevant to Issuance, Presentation, credential status, and DID support. It doesn't cover every lower-level dependency those standards rely on.
### Standards and profiles
#### Issuance and presentation protocols
These standards drive how an **Issuer**, **Verifier**, and **Holder** exchange requests, credentials, and proofs.
| Standard | Role in the platform |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
|
| Used inside OID4VP to express which credentials and claims a **Verifier** asks a **Holder** to present. |
#### Credential formats and status
These standards define what the credential looks like and how its status is checked.
| Standard | Role in the platform |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
|
| Experimental support for W3C Verifiable Credentials alongside the existing SD-JWT VC format. |
#### DID methods
These methods define how decentralized identifiers (DIDs) are created and resolved across the platform. A DID is a URI that resolves to a document holding the public keys and service endpoints needed to interact with its subject, without depending on a central registry or identity provider. The method name in a DID's prefix determines how that identifier is created and resolved - see [Decentralized Identifiers (DIDs) v1.0](https://www.w3.org/TR/did/).
| Standard | Role in the platform |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
|
| Experimental support for web-hosted DIDs with cryptographically verifiable change history. |
#### Profiles
These profiles and frameworks define requirements for specific credential ecosystems.
| Standard | Role in the platform |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
|
| Experimental support for high-assurance credential exchange interoperability. |
---
# 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.toolkit.equs.ai/docs/about-the-system/standards.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.
