> For the complete documentation index, see [llms.txt](https://docs.zcloak.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zcloak.network/developer-hub/guides/vc-operation/claim-attest.md). # claim-attest Assume a scenario where if you are the initiator of a contest, a contestant can claim an entry ticket, the contestant fills out the entry information and then initiates a review request to you, and you review and approve the contestant and issue an entry ticket to the contestant who meets the requirements. So in the above scenario, the contestant is Claimer and you (the initiator of the contest) are in the role of Attester. Claimer fills out the request and initiates a request to Attester to award a VC, and Attester reviews the request and decides whether or not to award a VC to Claimer. The VC issuance scenario described in the above procedure is the request mode of VC. In the following tutorials, you will learn how to initiate a VC issuance request to an Attester as a Claimer, respond to the request and construct a VC as an Attester, and endorse a VC as an Attester in conjunction with other Attesters. The following is a three-part introduction to each of the above three scenarios. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.zcloak.network/developer-hub/guides/vc-operation/claim-attest.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.