> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/help/comprehensive-overview-electronic-registries-and-verifiable-credentials/verifiable-credentials/what-are-the-components-of-verifiable-credentials.md).

# What are the components of Verifiable Credentials?

There are 3 main components of Verifiable Credentials:

1. **Credential Metadata:** A credential metadata consists of credential identifier and information to describe the properties of the credentials, such as certificate ID. It is cryptographically signed by an issuer.
2. **Claim:** A claim is an assertion made about a subject. It describes a quality or qualities, property or properties of a subject which establish its existence and uniqueness, such as vaccination details, government IDs etc.
3. **Proof:** A proof provides the information about the issuer of verifiable credentials,proving the authenticity of the issued credentials, such as issuer details, date of issue, time stamp, signature, etc


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rc.sunbird.org/help/comprehensive-overview-electronic-registries-and-verifiable-credentials/verifiable-credentials/what-are-the-components-of-verifiable-credentials.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.