Content provenance

Add verifiable provenance at creation.

C2PA signs the rendered file. Mnemo watermarks the embedding underneath. One API call on creation, one on verification.

01Where it applies

The vector-first filter.

If your pipeline generates content that starts as an embedding before render (creative, copy, synthetic media, enhanced product imagery), Mnemo applies.

02Why it matters

Provenance is moving below the rendered file.

Existing brand safety vendors detect fraud, viewability, and adjacency. None verify the creative's embedding.
03What this does

Registered at creation, checked later by your account.

The creative's embedding is watermarked and registered to your account at generation. Verification later, by the same account or namespace, reports whether a presented embedding resolves to that registered object. The result stacks with C2PA and complements the verification vendors you already use.

04Scope

What Mnemo does not do.

Does not detect prompt injection
Does not analyze model weights
Does not moderate content
Does not replace your system

Mnemo focuses on one layer: attaching identity to embeddings and verifying them when they are used.

Mnemo Verify checks whether a submitted vector resolves to an object registered to the caller's Mnemo account or namespace. verified=false is a safe outcome, not an error, and not proof that a vector is foreign. Verify does not establish the truth, authorship or ownership of the content behind a vector.

05Who this is for

Head of Brand Safety. VP Programmatic. CTO at DSPs, SSPs, ad networks, and holding companies. Chief Content Officer at publishing platforms.

06Why teams adopt it
  • Major platforms already require disclosure on generated creative.

Start verifying in minutes.

Start with a 30-day free trial.