VREC

Developers

The planned Evidence API uses one resource model with selectable assurance policies.

This website presents the proposed integration contract. The VREC API, SDKs, webhooks, sandbox, and chain registrar are not active in the current pre-launch phase.

Interface preview

No production endpoint or credentials are issued from this website.

Proposed request model

The proposed evidence request represents an event from the customer’s existing system.

POST /v1/evidence · design preview
{
  "external_record_id": "inspection-2026-1842",
  "record_type": "inspection_report_approved",
  "schema_version": "1.0",
  "issuer_id": "iss_organization_42",
  "document_hash": "sha256:8f4d...",
  "issued_at": "2026-07-10T14:30:00Z",
  "expires_at": null,
  "subject_ref": "inspection:2026-1842",
  "privacy": "restricted",
  "assurance": {
    "signature": "issuer",
    "timestamp": "rfc3161",
    "anchor_mode": "batch",
    "networks": ["solana", "arbitrum-one"],
    "finality": "final",
    "anchor_status_events": true
  },
  "metadata": {
    "policy_version": "INSPECTION-1.0",
    "source_system": "customer-platform"
  }
}
01

Idempotency will make retries safe.

Stable external references and idempotency controls are planned for every write operation.

02

Signed webhooks will report completion.

Evidence processing is designed around durable states and signed completion webhooks.

03

The request will state the assurance policy.

Customers will select signature, time, retention, disclosure, network, and anchoring policy.

04

Receipts will support portable verification.

Planned outputs include verification URLs, QR payloads, chain references, and downloadable proof packages.

Planned resource surface

The planned endpoints cover evidence, bundles, issuers, verification, usage, credits, and webhook testing.

POST/v1/evidenceCreate an evidence operation
GET/v1/evidence/{id}Read receipt and processing state
POST/v1/evidence/{id}/status-eventsAppend a signed lifecycle event
GET/v1/evidence/{id}/proofDownload a portable proof package
GET/v1/evidence/{id}/qrRetrieve the planned verification QR payload
POST/v1/verify/fileVerify a file against registered evidence
POST/v1/verify/dataVerify canonical data against registered evidence
POST/v1/bundlesCreate an Evidence Bundle
GET/v1/bundles/{id}Read an Evidence Bundle
POST/v1/bundles/{id}/evidenceAdd evidence to a Bundle
POST/v1/issuersCreate an issuer
GET/v1/issuers/{id}Read issuer identity and status
POST/v1/issuers/{id}/credentialsAdd an issuer credential
GET/v1/usageRead service usage
GET/v1/creditsRead service-credit balance
POST/v1/webhooks/testTest a planned webhook destination

Define the evidence event and assurance policy before implementing a connector.

Discuss an integration