Proof / Records
A number, months later, still provably ours.
Every successful run returns a record: a SHA-256 digest over the canonical JSON of the model name, spec version, inputs, and outputs. Store it next to whatever you built on those numbers. This page recomputes the digest from a stored response and tells you — match or mismatch — whether the numbers are exactly what that spec version produced.
The check runs server-side against the same code that minted the record. Nothing is stored.
What a match proves
That these outputs are byte-for-byte what the named spec version produced for these inputs — nothing was edited, rounded, or swapped after the fact. The spec version pins the exact formulas; the changelog shows everything that has changed since.
What it doesn’t prove
That the inputs were right for the situation, or that the model fit the question — a record is provenance, not judgment. To re-check numbers against the engine as it runs today, use POST /api/v1/verify/{model} in the docs.
Prefer to check it yourself?
You don’t need us for this. Build {model, specVersion, inputs, outputs}, serialize as JSON with object keys sorted recursively and no whitespace, and SHA-256 it. Both SDKs ship this as verifyRecord(). Or over HTTP:
curl -X POST https://worthune.com/api/v1/records/verify \
-H 'Content-Type: application/json' \
-d '{"model": "...", "specVersion": "...", "inputs": {...},
"outputs": {...}, "sha256": "..."}'