How can we help?
Most answers are in the documentation. For anything else, write to us.
Where to go
- DocumentationGuides for signing, watermarking, fingerprints and verification.
- QuickstartUpload, sign and verify a file with curl.
- API referenceEvery endpoint, generated from the OpenAPI contract, with reason codes.
- ConsoleAPI keys, jobs, verification, usage and billing.
- ContactEmail hello@originalpictures.com, book a call or find our address.
- Security disclosuresHow to report a vulnerability.
Common questions
How do I get an API key?
Create an account in the console. One button issues a key, and its default request signs with C2PA only.
Which file types are supported?
Sign, watermark and fingerprint: JPEG, PNG, WebP, TIFF, AVIF, WAV, MP3 and MP4. Sign and fingerprint: AAC audio in MP4. Sign only: further image, audio and video containers. A sidecar manifest covers documents, plain text, fonts and model files. The supported formats page lists every type and its upload limit.
Do I have to watermark or fingerprint?
No. The default request signs with C2PA Content Credentials only. Add a watermark by setting watermark to true, or fingerprints by setting fingerprint to true. Each is metered and billed on its own.
Do failed or cancelled jobs cost anything?
No. Processing is recorded only when a job publishes successfully. Failed, cancelled and not-yet-published work has no processing charge, and a retried publication cannot charge twice.
Why does a file I signed show no Content Credentials?
Content Credentials live in file metadata, and screenshots, many re-encodes and some CDNs remove them. If you added a watermark or fingerprints, a verification can search those signals; a match is reported as recovery, which is a lead, never cryptographic proof.
How do I report a security vulnerability?
Write to hello@originalpictures.com with the subject line "Security disclosure". We aim to acknowledge reports within one business day. The security page has the full policy.