Content Credentials after download: check the file you deliver
C2PA 2.2 defines Content Credentials and a separate Soft Binding API. Sume's docs do not say a downloaded output keeps one, so check the delivered file.
Sume's docs do not say that a generated file, or the copy you download from it, carries a C2PA Content Credential, so verify the file you actually deliver. The C2PA specification index, version 2.2, lists a Content Credentials specification and a separate Soft Binding API, but nothing on Sume's side ties the two together.
C2PA facts are from the specification index (listed under Sources) and Sume facts from Media inputs and Jobs and media, read 2026-09-30.
What does Sume say happens to an output?
Sume mirrors generated outputs into Sume-owned media URLs before exposing them in results, and tells integrations to store the Sume URL, not raw provider URLs. Completed jobs list artifacts with an id, URL, type and content type. The docs describe where the file lives, not how it is marked.
| Question | Answer in the docs |
|---|---|
| Where is the output? | A Sume media URL in result.artifacts[] |
| Can I save a copy locally? | sume jobs download <job_id> --output-dir ./out |
| Does it carry a C2PA record? | Not described |
| Is a provider URL exposed? | No, not a public output |
How do I check a file before I ship it?
Download it, keep the original bytes, and run your own C2PA-capable reader on that exact file, then repeat after every step you add, such as a re-encode or a platform upload. Record the result next to the job id so the answer is reproducible. Do not infer it from the model name.
sume jobs download job_123 --output-dir ./out
sha256sum ./out/* # keep the hash with the job idWhat are the limits of this answer?
The C2PA page read here is an index, so it does not describe manifests or watermarks in detail; consult the linked specifications for that. If a platform or regulator asks for provenance, treat the credential you can prove on the delivered file as the answer.
Sources
Related posts
More in Developers
- Can I continue a Sume Agent Completion with thread_id?
Not yet. Every Agent Completion runs in a fresh thread, so a follow-up call cannot reuse thread_id. Pass earlier results back in the next request instead.
- Crawl job finished event: Sume has none, poll crawl_get
Cloudflare publishes crawl.finished to Queues. Sume's crawl has no such event: wait on the job id, then read it with crawl_get. Steps and idempotency.
- curl 8.22 RFC 9421 signatures vs the Sume webhook signature
curl 8.22.0 adds experimental RFC 9421 HTTP Message Signatures. A Sume webhook is not one: it is an HMAC over timestamp.body in a sume-v1 header.
- Demand Gen image assets in every ratio from one reference
Loop one product reference through POST /v1/images to get the 1:1, 4:5, 9:16 and 1.91:1 Demand Gen image sizes, with notes on which pixel sizes are valid.
Written by Sume