Free public artifact
Certified Synthetic Dataset — Public Verification Sample
Access a free certified synthetic dataset with its machine-verifiable certificate, SHA-256 fingerprint, registry record, and public verification flow.
This is the canonical public example of how CertifiedData works. It is designed to let anyone inspect a certified artifact, understand the trust model, and see how verification, registry, and lineage fit together.
Definition
What is a public verification sample?
A public verification sample is a free certified synthetic dataset paired with a machine-verifiable certificate. It allows anyone to inspect the artifact, compare its fingerprint, validate its trust record, and confirm provenance through the public registry.
It exists to make the certification model openly inspectable. The point is not simply to distribute sample data. The point is to expose a live signed artifact inside a public trust system.
Why public matters
Trust infrastructure should be inspectable
Most synthetic data offerings still require a leap of trust. A buyer may receive a file and a set of claims about how it was generated, but the artifact itself is rarely exposed inside a public verification system.
CertifiedData makes one certified artifact openly available so the trust model can be examined directly. That allows builders, evaluators, technical reviewers, and potential buyers to inspect the mechanics of certification before going deeper.
This free route proves the artifact trust model. It shows how a dataset, certificate, fingerprint, registry record, and lineage context fit together in one machine-readable flow.
Included
What is included in the free public artifact
The public verification sample is intentionally simple and openly accessible. It is designed to give users a direct view into how CertifiedData certification works without requiring a paid step first.
A free certified synthetic dataset sample
A SHA-256 dataset fingerprint
A machine-verifiable certificate
A public registry record
A public verification path
Lineage to the parent dataset family
This artifact is free because the goal is broad inspection, understanding, and external validation of the trust model.
Verification workflow
How to inspect the sample
The sample is designed to make certification legible. You can review the artifact, inspect its fingerprint, confirm its trust record, and understand its provenance context using public surfaces.
Step 1
Access the artifact
Start with a real certified synthetic dataset that is openly available for inspection. The purpose of this sample is to make the trust model visible and testable.
Step 2
Inspect the fingerprint
Review the dataset fingerprint and compare it to the value recorded in the certificate. This ties the delivered artifact to the signed trust record.
Step 3
Validate the certificate
Use the verification flow to confirm the certificate is valid and that the artifact matches the corresponding record.
Step 4
Check the registry entry
Inspect the public registry to confirm issuance details, dataset metadata, and the surrounding provenance context.
Step 5
Follow lineage
Trace the sample back to its parent dataset family to understand how the artifact fits into the broader CertifiedData lineage model.
Registry and lineage
The artifact is part of a broader provenance chain
The sample does not stand alone as an isolated file. It sits inside a broader dataset family, with lineage that ties it back to its parent artifact context. That allows the sample to function as a lightweight public entry point into a deeper provenance model.
The registry provides the public record. Lineage provides the relationship structure. Together they make the artifact more than a download: they make it a traceable trust object.
Artifact record
Machine-readable artifact record
Structured summary for developers, evaluators, and AI systems.
Artifact record
{
"product": "Certified Synthetic Dataset — Public Verification Sample",
"slug": "public-verification-sample",
"route": "/public-verification-sample",
"canonical_url": "https://certifieddata.io/public-verification-sample",
"type": "free-certified-synthetic-dataset",
"category": "fraud-detection",
"price_usd": 0,
"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",
"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"
],
"discovery": [
"https://certifieddata.io/llms.txt",
"https://certifieddata.io/llms-full.txt"
],
"path_model": {
"this_path": "free — proves the artifact trust model",
"paired_path": "/verifiable-purchase-sample — proves the commerce trust model"
},
"concept_graph": {
"parent": "CertifiedData trust graph",
"children": [
"Certificate verification",
"Dataset fingerprint",
"Registry record",
"Artifact lineage",
"Agent Commerce provenance"
]
}
}Machine-readable trust hub
Public trust surfaces around the artifact
This sample sits inside a broader machine-readable trust hub. Verification, registry, documentation, discovery files, and contract surfaces make the system legible to humans, developers, evaluators, and automated agents.
Verify
Validate certificates, fingerprints, and trust records through the public verification surface.
Registry
Inspect public records for certified datasets, artifacts, and related trust context.
Docs
Review technical documentation, trust model explanations, and implementation surfaces.
llms.txt
Use the lightweight machine-readable discovery file for agents and crawlers.
llms-full.txt
Use the expanded discovery file for evaluators, developers, and machine consumers.
OpenAPI
Inspect the public machine-readable contract where available.
Agent Commerce
From free artifact verification to verifiable commerce
This free route proves the artifact trust model. It shows how a certified dataset can be made inspectable through fingerprint, certificate, registry, and lineage.
The paid route extends that same model into commerce. A verifiable purchase sample can connect the artifact to a purchase event, receipt, and transaction record so the commercial path becomes part of the provenance chain too.
Together, the two routes show how CertifiedData moves from certifying artifacts to supporting provenance-aware Agent Commerce.
Questions
Is this actually free?
Yes. The public verification sample is free and openly accessible. No account or payment is required to inspect the artifact, verify the certificate, or query the registry record.
What is the difference between the free and paid routes?
The free route proves the artifact trust model: dataset, certificate, fingerprint, registry, and lineage. The paid $0.99 route extends that model into commerce: it adds a verifiable purchase event, a signed receipt, and a transaction record linked to the artifact — showing how the same trust primitives extend into provenance-aware commerce.
Do I need a CertifiedData account to verify the certificate?
No. The verification surface at /verify and the registry at /registry are publicly accessible without an account. The signing public key at /.well-known/signing-keys.json is also public for independent signature verification.
What does 'machine-verifiable' mean?
Machine-verifiable means the certificate and artifact relationship can be checked programmatically without relying on the issuer's word. The dataset hash in the certificate must match the artifact. The Ed25519 signature must validate against the published public key. Both checks can be run by any party with access to the public key and the artifact.
How does lineage work?
Lineage connects this artifact back to its parent dataset family — the generation specification, algorithm configuration, and provenance context that produced it. Lineage makes the artifact traceable, not just verifiable.
Start here
Start with one public certified artifact
The public verification sample is the easiest way to inspect how CertifiedData works. It gives you a live certified artifact and the trust surfaces around it: certificate, fingerprint, registry, verification, and lineage.
Then, when you want to inspect how that trust model extends into commerce, move to the verifiable purchase route.
Machine pointers
- canonical_url
- https://certifieddata.io/public-verification-sample
- concept_type
- free-certified-dataset-verification-sample
- parent_concept
- CertifiedData trust graph
- related_concepts
- Certified synthetic dataset · Machine-verifiable certificate · SHA-256 fingerprint · Artifact registry · Dataset lineage · Agent Commerce
- verification_surface
- GET /api/certificates/verify/:id · GET /registry
- protocol_category
- dataset_certification