Live verification before persuasion
Reviewers land on a working verifier, not a claims page. They can hash a file in-browser, paste a digest, inspect JSON, or call the API.
Loading The VR School
Loading The VR School
MIT-style credential verification
The VR School Credentials is the public verification portal for hash-verifiable packets, W3C/Blockcerts-inspired credential envelopes, issuer-key status, revocation lists, and future blockchain anchors. It gives students portable proof and gives institutions a verifier they can reproduce, audit, and license.
Browser-side hashing keeps private student materials off the public internet.
Credential JSON is checked for issuer, subject, status, proof, and evidence surfaces.
Revocation, signer custody, and registrar review are visible before any chain claim.
Verified achievements connect back to learner portfolios and school workflows.
Verify a credential
Files are hashed in your browser. The verifier sends only the SHA-256 digest or credential JSON to The VR School verification API.
Choose a PDF or JSON file. The portal computes the digest locally before checking the registry.
Paste either hash to verify Ian Jiang's authenticated AP Seminar packets:
Primary handoff: 770a4119c542233fa68b767e65816ac0eb78eaa512a113363cf47acec8a3ccd4
Teacher-graded packet: 642b5b19546fd0348436eb1eeed90850114539931020e0fd03df7ff089d99ced
Beyond MIT-style verification
MIT's public credential portal made verification simple. The VR School keeps that clarity and adds learner privacy, registrar governance, role-based dashboards, and a path from classroom artifact to portable proof.
Reviewers land on a working verifier, not a claims page. They can hash a file in-browser, paste a digest, inspect JSON, or call the API.
Private student packets are verified by digest. The portal can prove integrity without publishing sensitive identifiers or private AP materials.
Issuer keys, revocation, review gates, signer custody, and no-chain-yet warnings are all explicit so trust is earned rather than implied.
Credentials link back into iBuildme, AP Seminar Studio, registrar dashboards, student portfolios, and institution-friendly APIs.
Proof stack
The experience is designed for a student showing their work, a registrar approving it, a district adopting it, and an external reviewer verifying it without special training.
Student work is represented by a SHA-256 digest so the verifier can confirm integrity without exposing private materials.
The system inspects W3C and Blockcerts-style structure, issuer identity, credential subject, status, proof, and evidence.
Public profiles, signing-key slots, revocation lists, and human review gates make the trust posture legible.
Verified credentials flow into student portfolios, registrar review, district reporting, admissions, scholarships, and wallets.
Authenticated packet registry
College Board can verify either private PDF by computing its SHA-256 digest and comparing it against the published registry below or the unified verifier API. Private documents are verified by fingerprint, not served publicly.
Private direct College Board handoff packet. Contains the full AP ID and is not served publicly.
Ian_Jiang_AP_Seminar_Portfolio_Packet.pdf
Authenticated supplemental teacher-graded packet for College Board or registrar review. Public verification is by digest only.
Jiang_UV12YZ72_AP_Seminar_Teacher_Graded_Packet_1.pdf
Redacted public preview that masks the AP ID and can be downloaded from the public site.
ian-jiang-ap-seminar-packet-preview.pdf
The full AP ID appears only in the private direct College Board handoff packet. Public verification uses the masked AP ID and cryptographic hashes.
Masked public AP IDCollege Board handoff
This packet is designed to be easy for a reviewer to verify without trusting the website blindly. The reviewer can compute the file digest locally, then compare or POST the hash.
Compute the SHA-256 digest of the private PDF and compare it to the private PDF SHA-256 above, or POST the hash to the verify endpoint as JSON: { "hash": "..." }.
The public verifier intentionally masks the AP ID. The full AP ID should be shared only through the private College Board handoff packet and official AP Digital Portfolio systems.
Verifier playbooks
The portal is meant to remove ambiguity during high-stakes review. A human can verify a packet, a district can evaluate governance, and a technical partner can integrate without guessing what proof stage the credential is claiming.
College Board or university reviewer
Compute the file hash locally, paste the digest, compare the returned artifact, and save the receipt with the review notes.
District or school administrator
Use the manifest, issuer profile, and revocation list to evaluate policy fit before expanding credential issuance.
Wallet, LMS, or SIS partner
Call the same verification API the browser uses, inspect credential status, and keep chain claims separate from hash proof.
Portable trust packet
The public surfaces below let partners inspect what is verified today, what remains gated, and how The VR School avoids premature blockchain claims.
Issuer keys
The portal exposes the same trust surfaces a verifier expects: issuer profile, active key slots, governance, and revocation. Production signatures remain locked until an authorized issuer key is published.
https://www.thevrschool.org/issuers/the-vr-school.json#ap-seminar-key-1
Status: awaiting-public-key
No production public key is published yet. This prevents accidental blockchain claims before registrar-approved signing.
https://www.thevrschool.org/issuers/the-vr-school.json#ibuildme-key-1
Status: awaiting-public-key
No production public key is published yet. This prevents accidental blockchain claims before registrar-approved signing.
Trust timeline
The portal is deliberately honest: hash verification is live, credential envelopes are live, registrar governance is live, and public blockchain anchoring waits for issuer keys and an anchored transaction.
live - Student packets and public previews are matched by deterministic SHA-256 hashes.
live - W3C/Blockcerts-inspired JSON envelopes can be verified against canonical hashes.
live - Registrar and credential-officer gates prevent self-approved official claims.
pending-key-publication - Official signatures unlock only after institutional issuer keys and custody are configured.
ready-next - Approved credentials can be batched and anchored once a public transaction workflow is active.
product-ready - Partners can license the trust model, verifier UI, APIs, governance workflow, and credential templates.
Verifier endpoints
https://credentials.thevrschool.org/api/credentials/manifest
https://credentials.thevrschool.org/api/credentials/verify
https://credentials.thevrschool.org/api/credentials/health
https://credentials.thevrschool.org/issuers/the-vr-school.json
https://credentials.thevrschool.org/issuers/revocation-list.json
https://credentials.thevrschool.org/api/ap-seminar/packet/manifest
https://credentials.thevrschool.org/api/ap-seminar/packet/review
API examples
A reviewer can use the browser. A district, university, or wallet can use the same source of truth over JSON. That is how credentials become infrastructure instead of a screenshot.
curl -X POST https://credentials.thevrschool.org/api/credentials/verify \
-H 'Content-Type: application/json' \
-d '{"hash":"770a4119c542233fa68b767e65816ac0eb78eaa512a113363cf47acec8a3ccd4"}'curl -X POST https://credentials.thevrschool.org/api/credentials/verify \
-H 'Content-Type: application/json' \
-d '{"credentialUrl":"https://credentials.thevrschool.org/api/ap-seminar/packet/credential"}'Who it serves
The same source of truth can power student portfolios, parent confidence, teacher review, registrar governance, district reporting, admissions checks, and partner licensing.
Students
Learners can carry verified accomplishments forward while keeping sensitive documents protected.
Schools and districts
District teams get verification APIs, registrar workflows, revocation posture, and licensing-ready governance language.
Colleges and reviewers
External reviewers can verify artifacts locally, compare digests, and inspect machine-readable credential status.
Ecosystem integration
Turn artifacts, courses, and projects into portable proof.
Open surface
Govern consent, review queues, issuer keys, signer batches, and revocation readiness.
Open surface
Use verified packets and rubrics without exposing private student identifiers.
Open surface
Verify hashes, issuer profile, revocation list, and credential JSON through stable APIs.
Open surface
Licensable trust OS
The VR School Credential Trust OS packages the portal, verifier APIs, credential templates, registrar workflow, issuer-key governance, revocation posture, and integration language into a practical trust layer for education and workforce partners.