Docs

Launch surfaces

Public pages designed for global adoption and partner building:

How it works Security Developers Partners Proof gallery Status Transparency Snapshot Weekly Digest Digest spec Conformance Hub Whitepaper (PDF)

This does not prove identity or legal admissibility. The Digest feed (JSON) is non-official and contains no user data.

ERF receipt object

{
  "payload": { ... },
  "signature": {
    "alg": "ed25519",
    "key_id": "...",
    "pubkey_b64": "...",
    "payload_b64": "...",
    "sig_b64": "..."
  }
}

The verify link is the source of truth.

Endpoints

POST /api/seal
POST /api/seal/batch
GET  /.well-known/evidex
GET  /api/receipt/:id
GET  /api/erf/:id  (application/erf+json)
GET  /api/verify/:id?client_hash_hex=...
GET  /api/certificate/meta?receipt_id=...
GET  /api/registry
GET  /api/registry/media-types
GET  /api/registry/algorithms
GET  /api/registry/profiles
GET  /api/registry/reason-codes
POST /api/certificate/pdf  (emergency fallback; disabled by default)
POST /api/certificate/badge.svg
GET  /api/private/:id?certificate_token=...  (optional)
POST /api/delete/:id
GET  /api/entitlement/status  (requires X-Evidex-Entitlement)
GET  /api/public-stats?days=7

Seal

POST /api/seal
{ "algo":"sha256", "hash":"<64-hex>", "mode":"free|pro", "label": {"display_name":"...","note":"..."} }

POST /api/seal/batch
{ "algo":"sha256", "items":[ {"hash":"<64-hex>","label":{...}}, ... ], "mode":"free|pro" }

Returns: receipt + delete_token + certificate_token. Label is stored as private meta and not shown publicly by default.

Certificate PDF

Default behavior: PDFs are generated locally in your browser (client‑side) to keep the service server‑light and to support offline/air‑gapped workflows.

• Provisional PDFs can be generated locally without a server PDF call.
• Final PDFs require an entitlement/quota check; if not entitled or blocked, the UI must generate a provisional PDF and show: “Provisional — Entitlement required for Final output”.

Emergency fallback (may be disabled): POST /api/certificate/pdf exists only for emergency pass‑through and returns a safe 410/404 when disabled.

Verification under disruption

Do not rely on primary-site availability alone. Keep exported receipt/proof/JSON where available, use offline/local verification helpers when possible, and retain independent records.

Read continuity guidance

Proof Story (light)

Evidence can be story-backed without becoming a social timeline: text + image, text + image + voice, or multiple related artifacts kept together with timestamps and explanatory notes.

This is packaging guidance only. No always-on capture, no surveillance flow, and no hidden lifecycle tracking.

Relationship Modes (light)

Templates and evidence narratives may be adapted for Casual, Business, or Formal / Ceremonial contexts. This changes tone and structure only; it is not a legal classification engine.

Acknowledgment / chat / voice entry (light)

A Vraimony flow may begin with a simple acknowledgment, a received/opened/seen style confirmation where appropriate, a simple voice confirmation in low-friction contexts, or a chat-friendly handoff. This does not turn Vraimony into a messenger platform or ambient recorder.

Safety disclaimer

Vraimony verifies integrity (hash/signature) and supports auditability. It does not prove identity, authorship, intent, or legal admissibility. No warranty.

Verify Widget (Embed)

Sandboxed iframe widget for third‑party sites. No tracking. Shows integrity status only.

Default view is minimal with a “Show details” toggle. Use the view param to start in expanded mode.

Open Widget Configurator Demo Embed playbook

Tip: If you embed the widget, allow frame-src https://www.vraimony.com in your site's CSP (iframe‑only embed). The widget does not store cookies or run any external scripts.

Education Pack (Universities & Institutes)

Batch issuance + registrar-friendly verification. Hash-only by default.

Overview Issuer Portal Public spec (markdown)

Standardization Pack

Public, stable docs that make ERF globally portable and integration-friendly.

ERF Standard Verify Protocol Registries Test Vectors Badge Policy

Discovery: /.well-known/evidex • Registry index: /api/registry

Billing provider (configurable)

Optional. Verify remains free. Billing configuration is deployment-specific and does not change privacy posture (no tracking).

Public billing notes

Checkout returns to /billing-success.html and saves the token locally.