CertifiedData.io

Commerce trust demo

Certified Dataset — Verifiable Purchase Sample

Inspect how a certified artifact, purchase event, and signed receipt can form one machine-readable provenance chain.

The free route proves the artifact trust model. This route proves the commerce trust model. Same cryptographic primitives — applied to a verifiable transaction, not just a dataset.

Two-path trust model

Artifact trust and commerce trust are different things

CertifiedData exposes two entry points into the trust graph. The free path proves the artifact model. This paid path proves the commerce model.

Free path

Public Verification Sample

Inspect a certified artifact and its trust surfaces for free. Proves the dataset fingerprint, certificate, registry, and lineage model.

Access free route →

$0.99 path

Verifiable Purchase Sample

Inspect the same artifact model plus a verifiable purchase event, signed receipt, and transaction record. Proves the commerce provenance chain.

You are here

Included

What you get for $0.99

Every item in this list is independently verifiable. The receipt and the certificate use the same Ed25519 signing infrastructure — different objects, same trust primitives.

Certified synthetic dataset

The artifact itself — 500-row fraud detection dataset generated by CTGAN. No real personal data.

SHA-256 dataset fingerprint

Cryptographic hash tied to the artifact. Any post-certification alteration changes the hash.

Machine-verifiable certificate

GENESIS certificate signed with Ed25519 over an RFC 8785-canonicalized payload. Verifiable by any third party.

Public registry record

The artifact's trust record in the public registry: certificate ID, issuance timestamp, trust level, and hash.

Verifiable purchase event

A commerce record linking the transaction to the artifact. Proves which artifact was purchased and when.

Signed receipt

An Ed25519-signed receipt linking the payment to the artifact, certificate, and transaction record — independently verifiable.

Provenance chain

How the chain connects artifact to purchase

The verifiable purchase sample makes a complete provenance chain visible: from the certified artifact through the purchase event to the signed receipt. Each link is machine-readable and independently verifiable.

1

Artifact

The synthetic dataset exists as a certified artifact with a SHA-256 fingerprint and signed certificate.

2

Purchase event

The transaction is recorded as a commerce event tied to the specific artifact and certificate.

3

Signed receipt

A receipt is issued: Ed25519-signed over a canonicalized payload linking artifact hash, purchase amount, and timestamp.

4

Registry record

The artifact remains queryable in the public registry independently of the purchase event.

5

Verification

Any third party can verify both the artifact certificate and the receipt hash against the published public key — no account required.

This route demonstrates not only a certified artifact, but also a verifiable purchase path tied to public trust surfaces. The artifact and the transaction remain independently auditable — neither requires trusting the platform that issued them.

Artifact record

Machine-readable artifact record

Structured summary for developers, evaluators, and AI systems.

Artifact record

{
  "product": "Certified Dataset — Verifiable Purchase Sample",
  "slug": "verifiable-purchase-sample",
  "route": "/verifiable-purchase-sample",
  "canonical_url": "https://certifieddata.io/verifiable-purchase-sample",
  "type": "verifiable-purchase-certified-dataset",
  "category": "fraud-detection",
  "price_usd": 0.99,
  "rows": 500,
  "columns": 12,
  "algorithm": "CTGAN",
  "certificate_type": "GENESIS",
  "signing_algorithm": "Ed25519",
  "fingerprint_algorithm": "SHA-256",
  "canonicalization": "RFC 8785 JCS",
  "verification_surface": "GET /api/certificates/verify/:id",
  "receipt_surface": "GET /api/payments/verify/:receiptId",
  "registry_surface": "GET /registry",
  "trust_level": "certified",
  "issuer": "CertifiedData.io",
  "proof_surfaces": [
    "https://certifieddata.io/verify",
    "https://certifieddata.io/registry",
    "https://certifieddata.io/.well-known/signing-keys.json",
    "https://certifieddata.io/agent-commerce/receipt"
  ],
  "discovery": [
    "https://certifieddata.io/llms.txt",
    "https://certifieddata.io/llms-full.txt"
  ],
  "path_model": {
    "this_path": "$0.99 — proves the commerce trust model",
    "paired_path": "/public-verification-sample — proves the artifact trust model (free)"
  },
  "concept_graph": {
    "parent": "CertifiedData trust graph",
    "children": [
      "Certificate verification",
      "Dataset fingerprint",
      "Registry record",
      "Artifact lineage",
      "Verifiable purchase event",
      "Signed receipt",
      "Agent Commerce provenance"
    ]
  }
}

Agent Commerce

The same model at Agent Commerce scale

Agent Commerce applies the same provenance-aware commerce architecture to autonomous AI agent spending. Every spend request is policy-governed, every transaction produces an Ed25519-signed receipt, and every receipt can be linked to the artifact, certificate, dataset, and decision record it funds.

The verifiable purchase sample is the minimal demonstration of that model: one artifact, one purchase event, one signed receipt, one verifiable chain.

Questions

Why is this $0.99 when the free route exists?

The free route demonstrates the artifact trust model: dataset, certificate, fingerprint, registry, and lineage. The $0.99 route demonstrates the commerce trust model: the same artifact plus a verifiable purchase event, signed receipt, and transaction record linked to it. They prove different things. The $0.99 is not a paywall on the free content — it is a separate technical demonstration of the provenance-aware commerce layer.

What makes a purchase 'verifiable'?

A verifiable purchase event produces a signed receipt that links the transaction to the specific artifact, certificate, and timestamp. The receipt is Ed25519-signed and independently verifiable by any third party against the published public key — without trusting CertifiedData or any intermediary.

How does this connect to Agent Commerce?

Agent Commerce is the framework for provenance-aware payments in AI agent systems. This purchase sample demonstrates the same proof primitives that Agent Commerce uses at scale: signed receipts, artifact linkage, policy-governed transactions, and independently verifiable provenance chains. The $0.99 purchase is a minimal live example of that model.

What is the difference between the certificate and the receipt?

The certificate proves the artifact was generated by CertifiedData and has not been altered since issuance. The receipt proves the purchase event — that a specific artifact was acquired in a specific transaction at a specific time. Together they create a provenance chain: artifact integrity + commercial event integrity, both independently verifiable.

Can I verify the receipt without a CertifiedData account?

Yes. The verification surface at /verify and the registry at /registry are publicly accessible. The signing public key at /.well-known/signing-keys.json is published for independent receipt signature verification.

Inspect the commerce trust model

One artifact. One purchase. One verifiable chain.

The verifiable purchase sample is the smallest practical demonstration of how CertifiedData extends the artifact trust model into commerce. Artifact integrity, purchase event, and signed receipt — all connected and independently verifiable.

Machine pointers

canonical_url
https://certifieddata.io/verifiable-purchase-sample
concept_type
verifiable-purchase-certified-dataset
parent_concept
CertifiedData trust graph
related_concepts
Certified synthetic dataset · Machine-verifiable certificate · Verifiable purchase event · Signed receipt · Agent Commerce · Provenance-aware payments
verification_surface
GET /api/certificates/verify/:id · GET /api/payments/verify/:receiptId
protocol_category
dataset_certification · agent_commerce
Certified Dataset — Verifiable Purchase Sample | CertifiedData | CertifiedData