Public verification

ProofLink API

ProofLink creates a tamper-evident receipt for autonomous IT actions. Each receipt can be checked independently through public verification endpoints, so auditors and operators can inspect what happened without trusting a private dashboard.

Verify a receipt

  1. 1. Copy a receipt ID from the public ledger or auditor report.
  2. 2. Call the verification endpoint with that receipt ID.
  3. 3. Confirm the receipt exists, the hash is present, and the chain is intact.
  4. 4. Use the auditor PDF when a shareable compliance artifact is needed.

Public endpoints

GET
https://verify.itechsmart.dev/api/verify/{receipt_id}

Verify one receipt by ID and inspect hash-chain evidence.

GET
https://verify.itechsmart.dev/api/stats

Read public ledger totals, chain integrity, and recent activity.

GET
https://api.itechsmart.dev/api/v1/verify/auditor-report.pdf

Download an evidence-first auditor report generated from live ledger data.

Live example

Example receipt: 011397ef5b714e33. This receipt is used as a public smoke-test reference for AG2 evidence review.

curl https://verify.itechsmart.dev/api/verify/011397ef5b714e33

Code samples

# Python
import requests

receipt_id = "011397ef5b714e33"
data = requests.get(
    f"https://verify.itechsmart.dev/api/verify/{receipt_id}",
    timeout=15,
).json()
print(data)

// JavaScript
const receiptId = "011397ef5b714e33";
const res = await fetch(`https://verify.itechsmart.dev/api/verify/${receiptId}`);
console.log(await res.json());

Bitcoin anchoring

ProofLink receipts are hash chained. OpenTimestamps anchoring is reported only when receipt metadata proves the attestation state. Auditor-facing language should distinguish live receipt generation from completed Bitcoin calendar attestation.

Open live ledgerAPI docs