Interactive demo

Generate it through us. It comes out cleared.

Follow Pip the Lantern Turtle — a fictional character from the Moonberry Grove world. Below, generate a real image of Pip on our rail: we check the license before any pixel exists, make the image, review the output, and hand you the asset with a signed receipt. Then watch the rights holder clear, monitor, and (when someone crosses the line) revoke. Both sides, one continuous story.

The controlled rail

Generate it through us → it's checked → cleared, with a receipt

Don't just clear a sentence — make the actual asset on our rail. We run the permission check before a single pixel exists, generate the image, review the output after, and hand you the image plus a signed receipt proving it was licensed. Nothing is saved; you can paste the receipt into /verify.

  1. 1Preflight

    Check the prompt against the license — generate only if it clears.

  2. 2Generate

    Make the real image through us (Olive Studio / Imagen).

  3. 3Postflight

    Review the pixels, then issue a signed, verifiable receipt.

No account · real image · real signed receipt

Just want to check a use without generating? Run the same engine as a one-call clearance:

Live

Try a real clearance call

Type what you'd make with the character. This runs the actual LicenseOS engine against a seeded license (Pixel Forge × Moonberry Grove) and returns a signed receipt — nothing is saved.

Rights-holder view: watch the AI Watch Bot scan your platforms and catch a misuse.

See the monitoring demo →

The developer side

  1. 1
    Clear before you ship

    One API call checks a planned use against the rights holder's rules and returns an instant allow / review / block — plus a signed receipt.

    API reference
  2. 2
    Generate, already cleared

    The generation proxy clears the prompt, generates, reviews the output, and stamps a content credential — so what you ship is provably licensed.

    Generation API
  3. 3
    Pull licensed assets

    List the IP's assets with per-asset permissions, then fetch one via a short-lived signed URL. Revoke, and the next fetch is denied — the kill switch bites.

    Asset API
  4. 4
    Prove it to anyone

    Every decision is a portable, signed receipt. Paste it into the public verifier — no account needed.

    Open the verifier

The rights-holder / brand side

  1. 1
    Publish your rules once

    Author a machine-readable license — what's allowed, where, by whom, at what price — content-hashed and versioned.

    For rights holders
  2. 2
    Watch the bot catch misuse

    Point the AI Watch Bot at a social/web image: it detects your character or brand and judges whether the use is on-license or a violation.

    How monitoring works
  3. 3
    Revoke — and it sticks

    Flip one switch. Active tokens keep resolving, but every new clearance and asset fetch is denied; the audit trail records who did what.

    Governance & control
  4. 4
    Bundle and get paid

    Aggregate opt-in IP into a flat-fee catalog; payouts split usage-weighted; each use still carries its own signed receipt.

    IP bundles

Drive it yourself

Two seeded accounts — sign in as either side. Password for both: licenseos-demo

Rights holder
studio@moonberry.test

Publish rules, run the Watch Bot, issue suitability certs, build bundles, revoke.

Developer
dev@pixelforge.test

Browse IP, get keys, run clearances, generate, pull licensed assets.