Provenance

Some Sigmora generation flows embed a provenance manifest in the files they produce: a signed record of the providers, models, prompts, seeds, retries, lineage and generation costs behind the media. Anyone can check that record.

Verify a file

Public, no account needed. Drop in a supported file and inspect its record.

Which outputs carry a manifest

Manifests come from Sigmora’s generative pipelines that use the Genblaze provenance format, such as brief-to-video generation. Not every output carries one: standard lesson renders, footage you supplied and some voice paths may not. When a flow runs, the result reports whether the manifest was embedded in the file. If embedding is not supported for that file, or fails, the record may be kept alongside the file instead, with a warning in the result.

Check the reported provenance state before telling anyone a file is self-verifying. A record kept alongside a file is not the same guarantee as one embedded in it.

Verify a file

The public verifier needs no account or API key and supports embedded manifests in PNG and MP4 files. It extracts the small manifest in your browser and checks only that record — the media file is never uploaded. To verify from code, extract the manifest JSON locally and send it to POST /v1/video/provenance/verify. Send the manifest only, never the media:

curl -X POST https://api.sigmora.org/v1/video/provenance/verify \
  -H "Authorization: Bearer $SIGMORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d @manifest-request.json

import json
import os

import requests

with open("manifest.json") as f:
    manifest = json.load(f)

verification = requests.post(
    "https://api.sigmora.org/v1/video/provenance/verify",
    headers={"Authorization": f"Bearer {os.environ['SIGMORA_API_KEY']}"},
    json={"manifest": manifest},
    timeout=30,
).json()["verification"]
print(verification)

import { readFile } from "node:fs/promises";

const manifest = JSON.parse(await readFile("manifest.json", "utf8"));
const { verification } = await fetch("https://api.sigmora.org/v1/video/provenance/verify", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SIGMORA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ manifest }),
}).then((r) => r.json());
console.log(verification);

Here manifest-request.json is {"manifest": { ... }}. Verification is free. The result reports the record’s hash integrity separately from whether every asset digest is present, so an intact record is never labeled as forged. A failed integrity check is a verdict about the record. It does not prove an unsupported file is malicious — first confirm the file type and whether the flow that produced it reported an embedded manifest.

What the cost record means

The costs in a manifest describe the generation steps that pipeline recorded. They are useful for auditing and comparing runs, but they are not your bill: some provider costs use representative pricing, and storage and delivery are outside the manifest. Your bill is the credits and creditBalance returned by the API and the totals in GET /v1/usage.

Models change; the manifest does not

Providers retire models, so the models behind a flow change over time. The manifest on a file is the historical record for that run. Treat it, not this page, as the truth about how a particular file was made.

Get started

Create

Grow & automate

Integrate

Build reliably

Operate

Verify a file

Which outputs carry a manifest

Verify a file

What the cost record means

Models change; the manifest does not

Verify a file

​Which outputs carry a manifest

​Verify a file

​What the cost record means

​Models change; the manifest does not

Which outputs carry a manifest

Verify a file

What the cost record means

Models change; the manifest does not