Certify any AI artifact
Drop a file to check or certify instantly. Every artifact gets a SHA-256 fingerprint and Ed25519 signature — independently verifiable by anyone.
Dataset · AI output · transaction record · published content artifact — any file, any surface, start free.
⬡
Drop any AI artifact to certify — free
Dataset · output · transaction record · content artifact — any file type
SHA-256 fingerprint computed client-side · no upload required to check
Four ways to certify
Every path produces the same cryptographic output — a certificate you can share, embed, or verify publicly.
Generate synthetic data
Choose a template or describe your schema. Generate a certified synthetic dataset in seconds.
Generate →⬆Upload & certify
Upload an existing dataset or AI output. We fingerprint, sign, and issue a certificate.
Upload →📋Templates
40+ industry schemas — finance, healthcare, fraud detection, energy, retail. Pick one and go.
Browse templates →📄Manifests
Submit a manifest for batch certification of artifacts, outputs, and dataset collections.
Submit manifest →What certification produces
Not a badge. A structured cryptographic artifact — independently verifiable by anyone without contacting CertifiedData.
Artifact fingerprint
SHA-256 hash computed over canonical artifact bytes. A stable, collision-resistant identifier tied to the exact artifact at certification time.
sha256: a3f8b21c4d9e…Signed certificate
Ed25519 signature over the full certificate payload. Verifiable with the published public key — no account or API access required.
ed25519: MEQCIHw…Registry entry
Certificate indexed in the public artifact registry — discoverable, linkable, and accessible via the verification API.
cert_01jt4x…Verification URL
A stable public URL that resolves the certificate and runs verification checks — shareable with anyone.
/verify?cert=cert_01jt…{
"certification_id": "cert_01jt4x…",
"issued_at": "2026-04-15T14:22:31Z",
"issuer": "CertifiedData.io",
"artifact": {
"sha256": "a3f8b21c4d9e7f6a…",
"filename": "synthetic_transactions.csv",
"rows": 50000,
"columns": 18,
"hash_algorithm": "SHA-256"
},
"algorithm": "CTGAN",
"schema_version": "cert.v1",
"signature": "ed25519:MEQCIHw…",
"verify_url": "https://certifieddata.io/verify?cert=cert_01jt4x…"
}Verify any certificate at certifieddata.io/verify — no account required.
Certification levels
All levels use identical Ed25519 signing infrastructure. Levels differ in metadata depth, proof chain complexity, and operational controls — not in cryptographic quality.
Sandbox
Testing, evaluation, and integration proof-of-concept.
SHA-256 hash · Ed25519 signature · 7-day retention · not registry-listed
{
"schema_version": "sandbox.cert.v1",
"certificate_id": "scert_7f3a9b2c1d…",
"sandbox": true,
"issued_at": "2026-04-15T14:22:31Z",
"expires_at": "2026-04-22T14:22:31Z",
"artifact": { "sha256": "a3f8b21c…", "filename": "dataset.csv" },
"signature_alg": "Ed25519",
"verify_url": "https://certifieddata.io/verify?cert=scert_7f3a…"
}Basic
Free-tier production use — persistent records, no volume cap.
SHA-256 hash · Ed25519 signature · persistent · registry-listed
{
"schema_version": "cert.v1",
"certification_id": "cert_01jt4x…",
"issued_at": "2026-04-15T14:22:31Z",
"issuer": "CertifiedData.io",
"artifact": {
"sha256": "a3f8b21c…",
"filename": "synthetic_transactions.csv",
"rows": 50000,
"columns": 18
},
"algorithm": "CTGAN",
"signature": "ed25519:MEQCIHw…",
"verify_url": "https://certifieddata.io/verify?cert=cert_01jt4x…"
}Verified
Build-tier workflows with policy metadata and differential privacy controls.
All Basic fields + policy_id · privacy_budget · dataset_lineage · batch_id
{
"schema_version": "cert.v2",
"certification_id": "cert_02kx9m…",
"issued_at": "2026-04-15T14:22:31Z",
"issuer": "CertifiedData.io",
"artifact": { "sha256": "b9c7d3e1…", "rows": 200000, "columns": 42 },
"algorithm": "CTGAN",
"policy_id": "policy_finance_v3",
"privacy_budget": { "epsilon": 8.0, "mechanism": "dp-sgd" },
"dataset_lineage": { "source_schema": "iso20022", "version": "2024-11" },
"signature": "ed25519:MEQCIHw…"
}Assured
Trust-tier with multi-party approval, signing key identity, and full audit trail.
All Verified fields + signing_key_id · approvers · audit_vault_entry_id · payload_sha256
{
"schema_version": "cert.v3",
"certification_id": "cert_03np2q…",
"issued_at": "2026-04-15T14:22:31Z",
"issuer": { "name": "CertifiedData.io", "signing_key_id": "key_ed_2026_01" },
"artifact": { "sha256": "c1e4f5a2…", "rows": 1000000, "columns": 56 },
"algorithm": "CTGAN",
"policy_id": "policy_healthcare_hipaa_v2",
"approvers": ["approver:a1b2c3", "approver:d4e5f6"],
"audit_vault_entry_id": "vault_entry_7f3a…",
"hashes": { "certificate_payload_sha256": "f9b3c7d1…" },
"signature": "ed25519:MEQCIHw…"
}Audit-ready
Govern-tier with full chain-of-custody, lineage bridge, and decision provenance.
All Assured fields + lineage_bridge_id · decision_log_ids · compliance_controls
{
"schema_version": "cert.v4",
"certification_id": "cert_04rq5s…",
"issued_at": "2026-04-15T14:22:31Z",
"issuer": { "name": "CertifiedData.io", "signing_key_id": "key_ed_2026_01" },
"artifact": { "sha256": "d2f5g6b3…", "rows": 5000000, "columns": 88 },
"policy_id": "policy_gdpr_article22_v1",
"approvers": ["approver:a1b2c3", "approver:d4e5f6", "approver:g7h8i9"],
"lineage_bridge_id": "lineage_01ab…",
"decision_log_ids": ["dlog_x1", "dlog_x2"],
"compliance_controls": ["gdpr-art22", "iso27001-a12.1"],
"audit_vault_entry_id": "vault_entry_8g4b…",
"hashes": { "certificate_payload_sha256": "a2c4e6f8…" },
"signature": "ed25519:MEQCIHw…"
}Machine-readable records
Every certification event produces structured JSON artifacts — designed for automated pipelines, verification scripts, and compliance tooling.
Certificate payload
The canonical JSON artifact signed by the Ed25519 key. Every field is included before signing — nothing can be altered without signature failure.
{
"certification_id": "cert_01jt4x…",
"issued_at": "2026-04-15T14:22:31Z",
"issuer": "CertifiedData.io",
"artifact": {
"sha256": "a3f8b21c4d9e7f6a…",
"filename": "transactions.csv",
"hash_algorithm": "SHA-256"
},
"algorithm": "CTGAN",
"schema_version": "cert.v1",
"hashes": {
"certificate_payload_sha256": "f9b3c7d1e5a2b4c6…"
}
}Verification response
What the /verify endpoint returns — structured for both human inspection and automated pipeline checks.
{
"verified": true,
"status": "valid",
"certificate_id": "cert_01jt4x…",
"issuer": "CertifiedData.io",
"issued_at": "2026-04-15T14:22:31Z",
"signature_alg": "Ed25519",
"artifact_hash_match": true,
"checks": {
"signature_valid": true,
"payload_hash_valid": true,
"not_revoked": true
},
"verification_url": "https://certifieddata.io/verify?cert=cert_01jt4x…"
}Artifact metadata block
Structured metadata recorded at certification time — preserved with the certificate for lineage and reproducibility.
{
"artifact_id": "art_9f2c3d…",
"sha256": "a3f8b21c4d9e7f6a…",
"filename": "synthetic_healthcare_v4.parquet",
"file_size_bytes": 18432000,
"rows": 500000,
"columns": 42,
"schema_version": "iso27799-2016",
"generation_algorithm": "CTGAN",
"source_type": "synthetic",
"certified_at": "2026-04-15T14:22:31Z"
}Manifest request
Batch certification via manifest — submit multiple artifacts in a single signed request.
{
"manifest_version": "1.0",
"submitted_at": "2026-04-15T14:22:31Z",
"artifacts": [
{
"sha256": "a3f8b21c…",
"filename": "train.csv",
"artifact_type": "synthetic_dataset"
},
{
"sha256": "b9c7d3e1…",
"filename": "validation.csv",
"artifact_type": "synthetic_dataset"
}
],
"policy_id": "policy_finance_v3",
"batch_label": "Q2-2026-training-data"
}How certification works
A six-step pipeline from raw artifact to independently verifiable proof record.
Canonicalize artifact
The artifact is serialized using a deterministic canonicalization scheme (RFC 8785 JSON Canonicalization for structured artifacts, raw bytes for binary). This ensures hash stability regardless of formatting or field order.
Compute SHA-256 fingerprint
A SHA-256 hash is computed over the canonical artifact bytes. This fingerprint uniquely identifies the artifact and detects any subsequent modification.
Bind metadata
The fingerprint is bound with structured metadata: issuer identity, generation algorithm, dataset dimensions, policy ID, schema version, and timestamp. The result is the certificate payload.
Sign with Ed25519
The canonical certificate payload bytes are signed using an Ed25519 private key. The signature is deterministic and short — 64 bytes. The corresponding public key is published and stable.
Issue verification record
The certificate, signature, and verification URL are written to the artifact registry and (for production tiers) the audit vault. The certificate becomes immediately verifiable.
Verify independently
Anyone can verify the certificate at /verify using the certificate ID. Verification recomputes the payload hash, checks the Ed25519 signature, and confirms registry status — no CertifiedData account required.
Certification surfaces
The same certification engine applies across every surface — datasets, outputs, transactions, and published content.
Synthetic datasets
Certify generated tabular data — CTGAN, Gaussian, or schema-controlled output. Each dataset gets its own certificate with algorithm metadata and row/column counts.
Synthetic data certification →AI outputs
Certify model completions, decision records, and inference outputs. Establish provenance for any artifact your AI system produces.
AI artifact certification →Agent Commerce
Policy-governed agent transactions with Ed25519-signed receipts. Every purchase, approval, or data exchange executed by an AI agent becomes a verifiable record.
Agent Commerce →Certified Publishing
Provenance records for machine-assisted content production. Establish authorship metadata, model attribution, and production timestamps for AI-assisted content.
Certified Publishing →Why certification matters
AI systems produce artifacts at scale. Without provenance infrastructure, those artifacts are unverifiable — by auditors, downstream consumers, or your own team.
Provenance
Certificates establish the origin of an artifact — where it came from, how it was generated, and when. This matters for regulatory submissions, procurement, and any system that ingests AI-produced data.
Tamper-evidence
Ed25519 signatures are mathematically unforgeable without the private key. Any modification to the certified artifact — even a single byte — invalidates the signature and is detectable at verification.
Reproducibility
Certificates record generation parameters: algorithm, schema version, row/column counts, policy ID. Teams can reproduce or audit the exact conditions of any certified artifact.
Independent verification
Verification requires no CertifiedData account, no API key, and no trust in CertifiedData itself — only the Ed25519 public key, which is published. Any party can verify any certificate without intermediary access.
Auditability
Higher tiers maintain an audit vault with chained, signed records. Each certification event is linked to its predecessor, creating a tamper-evident ledger suitable for compliance inspection.
Ready to run certification in production?
Free accounts include persistent records, registry listing, and production-grade Ed25519 certification — unlimited. Paid plans add policy depth, batch processing, audit vault, and operational controls.