Skip to content

FEDERATION

Run with the broader C2PA trust ecosystem.

Federate Hashproof with peer registrars. Federation documents, a manifest sync endpoint, and cascading resolution, without running your own registry.

What federation gives you

Four properties of every federated session. Document-based peering; cascading resolution on demand; a manifest sync endpoint for peers.

Peer registrar connections

Peer registrars exchange federation documents describing their endpoints. The protocol is designed to run behind mutual TLS in production deployments.

Peer federation documents

Each peer publishes a federation document describing its endpoints and capabilities. Hashproof fetches and validates it at registration.

Cascading resolution

When a lookup does not match locally, Hashproof can cascade it to federated peers and report which peer served the match.

Verification gating

A peer that fails verification is suspended and excluded from cascading lookups until it verifies again.

How a peer comes online

Federation is configured once. After the initial handshake, cascades run inside fingerprint resolve lookups when federation is enabled.

  1. 01

    Configure the peer endpoint

    Submit the peer registrar URL through the dashboard or POST /v1/federation/register. Hashproof fetches the peer federation document.

  2. 02

    Peer is verified

    Hashproof fetches the peer federation document and validates it. The peer becomes active once verification passes.

  3. 03

    Peer joins resolution

    The peer registrar is now part of your resolution surface. Unresolved lookups can cascade to it, and matches report which peer served them.

  4. 04

    Failed peers are suspended

    A peer that fails verification is suspended and excluded from cascading lookups until a later registration attempt passes verification.

Adding a peer

Federation is configured per node. Once a peer is added, unresolved lookups can cascade to it.

# Peers are added from the Federation tab in the dashboard
# (Scale and Enterprise). Your node registers with the peer over
# TLS, with no API key and no bearer token:

curl -X POST https://api.hashproof.ai/v1/federation/register \
  -H "Content-Type: application/json" \
  -d '{
    "nodeId": "9f2c8a1e-7b04-4d2a-9f3c-1e5a8c2d6b07",
    "federationDocumentUrl": "https://peer.example.com/.well-known/hashproof-federation",
    "callbackUrl": "https://peer.example.com/v1/federation/manifests"
  }'

# => {
#   "peerId": "c4f1a9d2-3e8b-4a6f-bb21-9d7e0f5a2c84",
#   "status": "pending_verification"
# }

Related capabilities

Federation is what turns a single registrar into part of an industry trust graph. It builds on the core verb triple.

Sign

Federation is most valuable when both endpoints sign. Issue C2PA manifests with managed keys, hybrid signatures, and Merkle anchoring.

Verify

Federation extends resolution across the broader trust ecosystem. When federation is enabled, an unresolved fingerprint lookup can cascade to registered peers.

Compliance reports

EU AI Act Article 50 reports from your stored manifests: per-manifest findings, summary counters, and a persisted report history.

Federation is on Scale and Enterprise.

Sandbox a peer connection on the Free tier; production federation unlocks at Scale ($299/mo). Enterprise tenants can co-locate registrars.