About 0byte

The origin protocol for AI content.

0byte gives every AI generation a fingerprint and a public proof of origin — who made it, with which model, and when. Anyone can check it, even from a screenshot.

The Problem

Every existing approach breaks in the same place.

They attach trust to the file. The internet strips the file.

Labels like C2PA get stripped the moment you upload to any platform. Watermarks only cover one vendor’s models and fade under screenshots and re-encoding. Standalone detectors hand you a probability with no evidence behind it.

None of them hold up where it matters — in a newsroom, or a courtroom.

The proof has to live outside the file, based on what the content looks like. That’s 0byte.

What 0byte does

One fingerprint. One public record.

Proof of origin that lives outside the file — verifiable by anyone, with detection as the safety net.

01

A fingerprint, not a label

0byte reads what the content looks like and turns it into a fingerprint. Screenshots, trimmed edges, color shifts, and re-uploads still match — and your image stays byte-for-byte identical.

02

A signed, public proof of origin

Every generation gets a digitally signed proof in an append-only public registry — who made it, with which model, and when. The same structure that secures HTTPS, so no one can quietly rewrite it.

03

Detection as the fallback

If content was never stamped, you still get an answer — an AI-detection score, clearly marked as a statistical estimate, not proof. The registry only gets stronger as more platforms stamp.

Where we fit

We complete the other approaches. We don't replace them.

C2PA and watermarks each solve part of the problem. 0byte is built for the part of the journey where they break — and surfaces their signals too when they survive.

C2PA labels

Signed metadata attached inside the file — stripped the moment a platform re-encodes it on upload.

Watermarks

Embedded pixels that only cover one vendor’s own models — and fade with screenshots and re-uploads.

0byte

Proof lives in a public registry, not the file — so it survives stripping and re-encoding. And when a label or watermark does survive, verification surfaces it too. One call, every signal.

How it works

Stamp at generation. Verify anywhere.

Stamping takes under 50ms and runs in the background. Verifying is free and needs no account.

  1. 01

    Stamp at generation

    Add 0byte to your pipeline in a single line. Stamping takes under 50ms and runs in the background — your users never feel it.

  2. 02

    Write to the public registry

    The fingerprint and a signed proof go into an append-only transparency log that only grows — auditable by anyone, rewritable by no one.

  3. 03

    Verify anywhere

    Send any content to one endpoint and get the origin back — provider, model, timestamp, signature. Free, and no account required.

  4. 04

    Fall back to detection

    No registry match? You still get a verdict — an AI-detection score, returned as a calibrated estimate rather than proof.

POST/v1/verify
// send any content, get back its origin:
{
  "match": true,
  "origin": {
    "provider": "Acme",
    "model": "Imagen 3",
    "created": "2026-03-14",
    "signature": "Ed25519 ✓"
  },
  "fingerprint_match": 0.99,
  "ai_detection": 0.04,
  "verdict": "registry_match"
}
The registry match — who, which model, when — cryptographically signed
Any surviving C2PA label or watermark, surfaced alongside
An AI-detection score when nothing's on record — marked as an estimate
What we don't do

The boundaries we hold by design.

We don't store the content

Only the fingerprint and proof metadata — never the image itself. The fingerprint can't be reversed back into your image.

We don't store prompts

Ever. They never touch our systems, and neither does any personal data.

We don't touch your files

No metadata injection, no watermarks. The image you ship is byte-for-byte identical to the one you made.

We don't require both sides

Verifying is free with no account. Detection works without stamping, and stamping works without anyone verifying.

Every generation, protected0bytebyte

Everything that passes through carries a signed proof of origin — provable anywhere it travels.

Where this is going

Every AI generation should be traceable to its origin.

Not through regulation or voluntary commitments — through infrastructure that makes it the default. 0byte is that infrastructure.