FAQs

Q: How does OpenOrigins differ from deepfake detection tools?

A: Instead of detecting AI fakes after they spread, OpenOrigins ensures provenance at the source, making fake content irrelevant. We prove authenticity at capture, instead of guessing authenticity after distribution.

Q: What media formats are supported?

A: OpenOrigins supports images, videos, and text files with cryptographic proofing. If there is sufficient interest, we will include audio files.

Q: Can I integrate with my DAM, MAM, S3 bucket, or other asset management system?

A: Yes. Use POST /v1/media/anchor during ingest, and store the returned anchor_id alongside your object metadata.

How do I get an API key?

Currently, you have to get in touch with the engineering team at OpenOrigins (email [e-mail]). But soon you will find it in the dashboard (Settings → API Keys).

What happens if a file is re‑encoded?

Re‑encoding changes the hash. Treat that as a new asset and anchor again.

Q: How do I start using OpenOrigins technologies within my organization?

A: Contact our team to discuss enterprise solutions, pilot programs, or API access. Reach out to [e-mail]