Monolith

Try it for real

What actually happens when you register an artifact.

Six steps, from a file on your disk to a signed C2PA manifest anyone can verify. Drop one of your own files below and the walkthrough runs on its real fingerprint, computed here in this tab.

Drop a file to use your own

Otherwise the walkthrough runs on a sample artifact. Hashing happens here either way; nothing is sent until you ask for it.

  1. 1

    Your file

    Pick any file — an image, a video, a PSD, a 4 GB archive. It is read and hashed here, in this tab. Images are then uploaded so the API can derive a perceptual hash and produce C2PA assets; everything else is registered from its fingerprint alone and never leaves your machine.

    Any file type
    Any size
    Hashed locally
  2. 2

    Fingerprint

    Your browser reads the bytes and derives a 256-bit digest. For a non-image, those 64 hex characters are the only thing that ever leaves the device — they identify the file uniquely without revealing anything about it.

    fingerprint: 0x6e500e2049c4a1f0b7d3a8c5e91f42b6d0c7a3e58b1f9d24c6a0e73f5b8a1b3f

    SHA-256
    Perceptual hash
    64 hex chars
  3. 3

    Mark & license

    The fingerprint is bound to one of your Marks, which carries the license, the visibility and your AI-training preference. This is the part you control.

    metadata.license

    Mark
    License
    Visibility
    AI training
  4. 4

    Signature

    Monolith signs the claim with a certificate recognised under C2PA. A signature has to belong to someone, so this is the step that needs an account — sign in and the rest of this runs for real, on your own artifact.

    signature

    C2PA conformant
    signature
    publicKey
  5. 5

    On-chain anchor

    The signed claim is written to chain. The transaction hash is what turns “we say this existed on this date” into something an outsider can verify independently. On a real run the block below waits here until the chain actually takes it.

    transactionHash

    transactionHash
    Immutable
    Public
  6. 6

    C2PA manifest

    You get back a signed manifest and an artifact page in your workspace. Drop the fingerprint into the verifier and the whole chain — file, mark, license, signature, anchor — resolves in one request.

    c2paAssets.manifestUrl

    Manifest URL
    Artifact page
    Verifiable

That whole pipeline is one API call.

You send a fingerprint and a mark. You get back a signed, anchored, C2PA conformant manifest. The file stays where it is.

Get StartedRead the Docs