CertifiedData · Manifest Intake
Submit a manifest for certification
A manifest is a structured description of an artifact and its provenance context. Submit one to certify complex artifacts, batch collections, or outputs with rich lineage — all through a single certification request.
Manifests support every certification surface: datasets, AI outputs, published content, and Agent Commerce artifacts.
When to use manifest-based certification
Single-file drop works for most cases. Use a manifest when your artifact has more structure than a single file can express.
Batch certification
Submit a collection of artifacts in one manifest rather than certifying each individually.
Automated pipelines
Integrate certification into CI/CD, data pipelines, or content workflows — submit manifests programmatically.
Complex provenance
When an artifact has multiple source references, parent lineage, or multi-step generation — a manifest captures all of it.
Audit and replay
Manifests support certification replay — re-issuing a certificate from recorded inputs for audit trail completeness.
What a manifest contains
Each field maps to a verifiable claim in the issued certificate.
| Field | What it records |
|---|---|
| artifact_type | What kind of artifact this is — dataset, output, published-page, bundle, or custom. |
| content_hash | SHA-256 fingerprint of the artifact payload. Can be pre-computed client-side. |
| source_references | Input documents, model IDs, prompt versions, or retrieval sources used to produce the artifact. |
| generation_metadata | Model name, version, sampling parameters, or pipeline configuration recorded at time of generation. |
| lineage | Parent certificate IDs or upstream artifact references — links this artifact to its predecessors. |
| policy_context | Optional policy ID or approval reference — links certification to an Agent Commerce policy decision. |
| issuance_notes | Free-form metadata field for custom context, environment, or workflow identifiers. |
{
"artifact_type": "dataset",
"content_hash": "sha256:a3f8…",
"source_references": ["schema://finance/transactions-v2"],
"generation_metadata": {
"algorithm": "CTGAN",
"rows": 50000,
"columns": 18
},
"lineage": ["cert_01jt…"],
"policy_context": "pol_01js…",
"issuance_notes": "Q2 2026 training batch — approved by data-ops"
}How manifest certification works
Same certification engine as every other surface. The manifest is the structured input format for complex or automated workflows.
Prepare the manifest
Describe the artifact — type, content hash, source references, generation metadata, and any lineage or policy context.
Submit via API or dashboard
POST the manifest to the certification endpoint. The engine validates the structure and computes a fingerprint of the manifest payload itself.
Certificate issued
An Ed25519-signed certificate is returned. It records the artifact fingerprint, bound metadata, issuer, and timestamp.
Verify anytime
The certificate ID can be shared or embedded. Anyone can verify it at /verify — no account required.
Ready to submit a manifest?
Manifest submission is available via the platform API and dashboard. The full schema reference is in Docs. If you are integrating a publishing pipeline or data workflow, contact us to discuss implementation.