Skip to content

PRODUCT OVERVIEW

Everything Hashproof does, on one page.

Sign C2PA manifests, resolve them across re-encodes and crops, and verify cryptographic integrity through one HTTP API. Below: the three core pillars, six secondary capabilities, and the 4-step pipeline they assemble.

Core pillars

Secondary capabilities

Six capabilities that don't appear on the landing page. Available on Scale and Enterprise; noted per row.

Compliance reporting

EU AI Act · Aug 2026

Structured EU AI Act Article 50 reports generated from your stored manifests. One synchronous endpoint returns per-manifest findings and summary counters as JSON.

Post-quantum signatures

FIPS 204 · NIST PQC

An additive ML-DSA-65 assertion alongside classical ES256. On runtimes without ML-DSA support the assertion is a labeled simulation.

CMAF streaming

Live streaming

Per-segment hash records for live video streams. Attach provenance records to fragments without re-encoding.

Federation

Federation · cascade

Multi-registrar federation between Hashproof nodes. A manifest sync endpoint and cascading resolution for unresolved lookups, without running your own registry.

Training-data lineage

Attestry bridge

Register dataset manifests; query whether a given asset was part of a training run. Cross-links provenance with AI training provenance.

Forensic verification

Insurance · newsroom

Manipulation signals with a structured confidence score. Built for insurance claims, newsroom authentication, and legal discovery.

Architecture

Client traffic resolves DNS through Cloudflare, is authenticated at the Hashproof API, and fans out to four specialized data planes.

Hashproof architecture diagramClient apps call the Hashproof API on Railway, with DNS via Cloudflare. The API fans out to Supabase Postgres, Upstash Redis, S3-compatible object storage, and Merkle batch anchoring.Client app / SDKTypeScript · cURL · PythonCloudflare DNSname resolutionHashproof APIFastify · Railway us-west2PostgresSupabasemanifests, keys, usersRedisUpstashrate limiting, cacheObject storageS3-compatibleraw manifests, computed CIDsMerkle batchinclusion proofsmanual anchoring runs

The pipeline

Four endpoints, one HTTP API. Signing writes; resolution and verification read.

  1. 01

    Sign

    POST a binary with a title; receive a signed manifest + CID.

  2. 02

    Store

    Manifest lands in object storage and Postgres, eligible for the next Merkle batch.

  3. 03

    Resolve

    Given a transformed binary, return ranked manifest candidates.

  4. 04

    Verify

    Return signature, trust, and validation detail in one structured response.

Minimal verification

One request returns signature validity, trust-list match, and validation detail.

curl -X POST https://api.hashproof.ai/v1/verify \
  -F "file=@/path/to/image.jpg"

# => { "hasProvenance": true, "trustStatus": "trusted", "source": "embedded",
#      "manifest": { ... }, "validation": { ... } }

Ship provenance this afternoon.

Free tier includes 1,000 signed manifests per month and 10,000 verifications. No credit card.