KYC and onboarding

Use case

Identity and onboarding flows take photos of documents and faces. ChronoVerify checks the capture-time and provenance integrity of those images and keeps a signed record, as one layer alongside your identity provider.

The workflow

Verify the captured image. Run the document or selfie image through the API at capture.
Check for tampering signals. Read metadata consistency and pixel-forensic flags; validate any Content Credentials.
Keep a signed audit record. Generate a signed, timestamped report for your compliance file.

Which verdicts matter

Use metadata_anomaly and manipulation_indicated as review triggers in your onboarding flow. The signed report is the durable artifact for your compliance record.

What this can and cannot tell you

ChronoVerify is a provenance and integrity layer, not an identity-verification or liveness product, and it is not a deepfake detector. Use it alongside a dedicated identity provider, and never make an identity decision about a person on a verdict alone.

One call

curl -X POST https://chronoverify.com/v1/verify \
  -H "Authorization: Bearer cv_live_..." \
  -F "file=@document.jpg"

Omit the Authorization header to use the free, rate-limited public path. Full field reference is on the method and API page.

Common questions

Is this an identity-verification product?

No. It verifies a photo's capture time and provenance integrity. It complements an identity provider's document and liveness checks; it does not replace them.

Does it detect a deepfake selfie?

No. It is provenance-first and reports metadata and forensic signals for human review; it is not a deepfake or liveness detector.

See a verdict on a real photo.

Try the free verifier