Capture and sign on trusted devices
ProofSign gives the mobile client signing config, checks device trust, and signs first-party captures.
ProofSign signal board
v0.1.0
No slop. All human provenance.
ProofSign is the public signing service behind Divine's first-party capture flow. It helps us prove a loop came from a real device and moved through our own pipeline.
Check the receipts
Paste a Divine video URL, Nostr event ID, nostr: link, media URL, or a raw SHA-256.
Resolved URLNot checked yet
Resolved event IDNot checked yet
SignerNot checked yet
ProofMode detectedNot checked yet
Capture deviceNot checked yet
Capture timeNot checked yet
Content hashNot checked yet
Failure codesNone
How Divine keeps it human
The product claim is simple: if Divine says a loop came through our first-party pipeline, there should be receipts to back that up.
Verify server-side before trusting it
Divine runs the resulting media through our verifier before we lean on the provenance state.
Show signed and unsigned media clearly
Signed first-party media, unsigned uploads, and broken credentials should not all look the same.
Main endpoints
Configuration is public. Signing and verification-adjacent flows stay guarded.
/health
Simple service health check.
/api/v1/c2pa/configuration?platform=ios|android
Public signing configuration for the mobile client.
/api/v1/c2pa/sign?platform=ios|android
Remote C2PA signing for trusted callers.
/api/v1/verify/lookup
The branded front door for public verification lookups on this page.
Learn more
If you want the standards and the wider context, start here.
C2PA overview
What Content Credentials are, where the standard came from, and why provenance matters.
C2PA FAQ
The standards-side answer to what C2PA can and cannot promise.
ProofMode
The wider provenance ecosystem ProofSign is building on top of.
Divine ProofMode spec
How Divine carries authenticity data through Nostr video events.
Divine media resources
Public-facing context on how Divine talks about authenticity and AI slop.