Vitrified documentation

Vitrified is a structured cryptographic attestation service. You submit a content hash plus structured metadata via authenticated API; Vitrified aggregates submissions into Merkle batches and witnesses each batch root through six independent trust mechanisms in parallel. You receive a per-submission proof bundle that is independently verifiable against the relevant public trust infrastructure — without trusting Vitrified or any specific witness provider.

The bytes of your artifact never cross our wire. You hash locally; Vitrified receives the hash plus structured metadata.

Start here

• Quickstart — install the SDK, submit your first attestation, verify the returned bundle.
• Concepts — the six witnessing mechanisms, the shape of a proof bundle, canonicalization, submission policy.

Reference

• JavaScript / TypeScript SDK
• Python SDK
• Verifier CLI
• GitHub Action
• MCP server
• API reference

Hosted services

• api.vitrified.glass — the witnessing engine REST API.
• verify.vitrified.glass — in-browser bundle verification; same library you can embed in any web property via @vitrified/verifier-web.

What Vitrified is not

• Not a QTSP. eIDAS-qualified status comes from the QTSP signature embedded in the timestamp token, not from any claim Vitrified makes.
• Not a hashing-on-our-side service. You hash locally; we receive the digest.
• Not a proprietary verification path. Every mechanism verifies against its standard public trust infrastructure with that mechanism's reference tooling.
• Not lock-in storage. Full programmatic access to every attestation, every bundle, every audit log entry from day one.