Pittro/verifiable-ai-provenance-bench

Verifiable AI Provenance Bench (TTTPS)

25 real timestamp-provenance receipts generated on 2026-08-04 by calling the live KPP (Kenosian Protocol Platform) provenance API (POST /v1/anchor, POST /v1/verify), which implements the TTTPS (Time-Token Tamper-evident Provenance Seal) scheme. Each row is one real API round trip: a content_hash was submitted to /v1/anchor, the returned receipt_id was then submitted to /v1/verify, and both raw responses are recorded.

This dataset was built while integrating TTTPS receipt-sealing into eight AI-tooling frameworks (LangChain, LiteLLM, LlamaIndex, smolagents, vLLM, Ollama, Ragas, DeepEval) plus a standalone OpenAI-compatible proxy (openttt-proxy). The framework column identifies which integration context each sample content string represents; the sample_description is a short label, not the raw payload itself (TTTPS never sends raw payloads to the server — only a client-computed sha256 digest is transmitted).

What this is NOT

This is not a benchmark of model outputs, and it is not a claim of any third-party endorsement. It is a small, honest sample of real cryptographic timestamp receipts from one provenance service, published so the receipt schema and round-trip behavior can be inspected independently. No inference calls to any LLM provider are included.

Generation method (exact, no embellishment)

1. Issued one free API key via POST https://kpp.kenosian.com/v1/keys.
2. For each of 25 sample descriptors, computed content_hash = "sha256:" + sha256(text).hexdigest() locally (the underlying text never left the client).
3. Called POST https://kpp.kenosian.com/v1/anchor with {content_hash, key} — recorded the full AnchorResponse JSON.
4. Called POST https://kpp.kenosian.com/v1/verify with {receipt_id} — recorded the full VerifyResponse JSON.
5. All 25/25 anchors returned verified: true on immediate re-verification.

No records were fabricated, padded, or resampled from prior sessions. This is the complete, unfiltered output of the generation run (25 requested, 25 succeeded).

Schema (tttps_receipts.jsonl, one JSON object per line)

field	source	description
framework	local	which integration context this sample represents
sample_description	local	short label for the (never-transmitted) source text
content_hash	local, sent to API	sha256:<hex> digest submitted to /v1/anchor
receipt_id	API (AnchorResponse.receipt_id)	opaque id, also the verify lookup key
receipt	API (AnchorResponse.receipt)	Ed25519/HMAC-SHA256 signature over time+hash (server's own field description)
time	API (AnchorResponse.time)	sealed timestamp, UTC ISO-8601
time_source	API (AnchorResponse.time_source)	e.g. roughtime_chain (independently witnessed) or local
roughtime_k	not emitted by the API	always null in every row. The collector read a roughtime_k key that AnchorResponse does not define, so the column carries no information. Witness state is published separately at GET /v1/time/health.
backdating_p	API (AnchorResponse.backdating_p)	upper bound on probability of forging an earlier-dated valid receipt
verify_url	API (AnchorResponse.verify_url)	relative path, combine with https://kpp.kenosian.com
quota / used	API (AnchorResponse)	free-tier quota bookkeeping on the key used for this run
verified	API (VerifyResponse.verified)	boolean, result of the immediate re-verify call
verify_reason	API (VerifyResponse.reason)	server's own human-readable verification reason string

Every field above sourced from the API uses the server's own name, with no renaming, with the one exception called out in the table. The published schema for these endpoints is https://kpp.kenosian.com/tttps-openapi.json, rendered at https://kpp.kenosian.com/tttps-api.html.

Reproduce / verify independently

Any receipt_id in this dataset can be independently re-verified right now:

curl -s -X POST https://kpp.kenosian.com/v1/verify \
  -H "Content-Type: application/json" \
  -d '{"receipt_id": "9a29b0048aa54af1687d41aa"}'

Verification is open and needs no credential, which is the point: these receipts can be checked by anyone without asking the issuer for anything. Any of them can also be exchanged for an offline-verifiable certificate via POST /v1/export/certificate, a W3C Verifiable Credentials 2.0 document whose Ed25519 proof checks against the public key at GET /v1/tttps/did.json with no call back to the service.

Live interactive explorer: https://huggingface.co/spaces/Pittro/tttps-proof-explorer

The framework column names an integration context, not a shipped package. Which integrations are installable today, with the exact install command for each, is published in one place and is not restated here: https://kpp.kenosian.com/tttps-api.html#integrations.

Honest limitations

• 25 records is a small, single-session sample, not a large-scale benchmark — sized to stay well within the free-tier quota (1000/key) and avoid unnecessary server load.
• sample_description text is a synthetic label written to represent each integration's typical output context; it was never sent to any LLM provider or to the KPP server (only its hash was transmitted, by design of the protocol).
• This dataset demonstrates the timestamp/tamper-evidence receipt layer only. It does not evaluate or claim anything about the correctness of any AI model's output — the server's own field description is explicit that a receipt proves when and tamper-evidence, not correctness.