> For the complete documentation index, see [llms.txt](https://guide.transmute.industries/verifiable-data-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.transmute.industries/verifiable-data-platform/learning-center/verification-validity-and-veracity-checks.md). # Verification, Validity, and Veracity Checks As you learned in our talk about holders, issuers, verifiers, and subjects, a verifier verifies a credential that someone is holding. But what does that really mean? When a credential is “verified” that means that it has gone through one or more of the following three checks: **verification**, **validity**, and **veracity**. A **verification** check tests that a credential has been formatted correctly. In Transmute’s platform that means checking to make sure that a credential meets the requirements of the W3C verifiable credential data model. The verification check also makes sure that the linked data contained in the verifiable credential meets certain standards. A **validity** check tests that a credential has the appropriate signature/proof and that the credential hasn’t been tampered with. As you learned in our piece on digital signatures, this is the digital, higher security version of checking a written signature. A **veracity** check tests that a credential has use-case specific details or fields necessary for it to be valuable. For example, a customs organization may require an associated purchase order number on every commercial invoice for in-bound shipments. A veracity check can be coded in customs’ system to make sure that every commercial invoice has a purchase order number contained within it in order to be considered for facilitation benefits. Verifiable data issued on the Transmute platform includes both verification and validity checks in the security tab of each credential. Veracity checks are decided by each business, and Transmute works with each customer to ensure that required fields are correctly defined in order to support this verification need. --- # 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://guide.transmute.industries/verifiable-data-platform/learning-center/verification-validity-and-veracity-checks.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.