Skip to main content
Encypher Logo

For publishers and IP holders

Publish once. Keep identity and rights attached.

Set your licensing terms once and they travel with every article. Build a dated, source-linked record you can take into a licensing conversation, and identify which distributed copy a leak came from.Verify the publishing domain, mark each article or asset before distribution, attach machine-readable rights terms, and retain a source-linked evidence trail for readers, partners, and licensing teams.

Unlimited

free signing for normal publishing use, fair-use guardrails apply

8 file types

text, image, audio, video, PDF, DOCX, XLSX, and PPTX through one API

Under 20 min

typical setup on WordPress, Ghost, or your own CMS

Flagship workflow

Publish with identity and rights terms attached

Mark binds identity and terms at publication. Meter records bounded evidence of use for licensing review. Trace identifies which distributed copy a leak came from. Rights terms are what the publisher supplied, not a determination of ownership.

Available now

Workflow

  1. 1

    Mark binds identity and machine-readable terms at publication

    Confirm domain control, then sign text, images, audio, video, PDF, DOCX, XLSX, or PPTX as content leaves the CMS, with the applicable W3C ODRL rights profile bound to the content at signing time. DOCX, XLSX, and PPTX sign under C2PA 2.4 and verify version-agnostically; they are not formal C2PA Conformance Program formats.

  2. 2

    Meter records bounded evidence of use for licensing review

    Early partner program. Encypher observes per-source verification results, with a named reason when a check does not pass. Retrieval, grounding, and citation events are supplied by the partner AI company. What was established and what was not stays labelled on the record.

  3. 3

    Trace identifies which distributed copy a leak came from

    Give each embargo recipient or syndication partner a distinct marked copy. When a preserved marker is recoverable from a leaked document, it resolves to that recipient's distribution record. It identifies the copy, not the person who moved it.

Product roles in this workflow

MarkAvailable now

Bind portable provenance and verified terms to a content object or completed output.

MeterEarly partner program

Record observed retrieval, citation, and other partner-supplied events for bounded usage reporting.

TraceAvailable now

Connect a distributed copy to its intended recipient or event.

Illustrative publication record

One article, one source-linked review record

The article identity and source record stay attached as publishing evidence moves into licensing review.

Canonical article source

publisher.example/articles/coastal-freight-outlook

PUB-2026-0618-014

  1. 01Source: PUB-2026-0618-014

    Article published

    "Coastal Freight Outlook" published June 18, 2026 at 14:05 UTC.

  2. 02Source: PUB-2026-0618-014

    Publisher identity verified

    Domain control verified for The Daily Ledger at publisher.example.

  3. 03Source: PUB-2026-0618-014

    Rights terms supplied

    Publisher-supplied profile requests attribution for citation and a licensing contact for training.

  4. 04Source: PUB-2026-0618-014

    Verification recorded

    Public verification at 14:12 UTC matched the signed article source.

  5. 05Source: PUB-2026-0618-014

    Licensing review opened

    Source record, supplied terms, and verification event assembled for counsel and licensing staff.

  6. 06Source: PUB-2026-0618-014

    Review status

    Open - counsel review pending; no legal determination recorded.

Evidence received

  • Verified publisher identity, rights snapshot, and content-integrity status
  • Source-linked signing and verification record for licensing review
  • Per-source verification results carrying a named reason when a check does not pass

Rollout path

  • Sign one article free, then connect the CMS publication hook
  • Backfill priority archives and issue recipient-specific Trace copies for embargoed material
  • Apply to the Meter early-partner program when licensing review needs usage evidence

Mark can bind a verified publisher identity and rights terms to content. It does not prove that the signer legally owns the copyright.

What you can use today

Live now, live paid, early partner, roadmap

Each rung carries its own status. Nothing here is described as available before it is.

  1. 01Live now

    Publish and verify with Mark. Sign each article through WordPress, Ghost, a webhook, or the API, then give readers a public verification path. The dashboard retains the signed source record and provenance checks.

  2. 02Live now

    Issue recipient-specific copies with Trace. Give each embargo recipient or syndication partner a distinct invisible marker. When a preserved marker is recoverable from a leaked copy, it resolves to that recipient's distribution record.

  3. 03Live paid

    Investigate external-domain detections. Attribution Analytics adds confirmed detections on verified external domains, linked back to the signed source for licensing teams to investigate.

  4. 04Early partner

    Review supplied usage events with Meter. Meter combines observed signals with partner-supplied usage records. Coverage limits remain explicit, and the resulting record supports licensing review.

  5. 05Roadmap

    Extend the licensing workflow. Formal Notice packages and a licensing marketplace are planned workflow additions, not live product capabilities.

See it in action

Try the publisher demo

Paste an article, sign it, and verify the invisible proof, right here on the page. No account, no API key.

Interactive demoTry it below: paste, sign, verify.
1

Paste your content

Sample article pre-filled. Edit it or paste your own.

Free to try

Paste your text and go. No account, no setup.

Invisible to readers

The mark is hidden inside the text. Anyone reading it sees exactly what you wrote, nothing different.

Anyone can check it

It uses an open standard Encypher helped create, so anyone can confirm where the text came from.

Licensing and evidence

Set your terms. Build the record behind them.

After domain verification, your W3C ODRL rights profile travels with signed content. The free dashboard records provenance checks; paid Attribution Analytics adds confirmed external-domain detections. You control licensing decisions and outreach.

Example W3C ODRL rights profile

Bronze (crawling)
Permitted, search indexing fine
Silver (RAG/citation)
Permitted, author name and canonical URL required
Gold (training)
License required, contact licensing@yourorg.com

The profile is expressed in W3C ODRL. A rule either permits or prohibits a use; a licensing requirement is a commercial term layered on a permission, not an ODRL decision. The profile records the terms the publisher supplied at signing time, evidence of what was stated rather than a determination of who owns the work.

Set the profile once for signed content. Revenue from direct deals remains yours; source records and confirmed detections support pricing and partner review. If you want Encypher to broker deals, join the opt-in Coalition.

What the record settles, and what it does not

Signed source records, publisher-supplied terms, and verification history give counsel dated technical material to examine. They show what the publisher supplied, when the source was signed, and what Encypher recorded. They do not by themselves prove ownership, infringement, notice, willfulness, or damages. Counsel must assess the facts, applicable law, and legal significance.

US statutory damage ranges, for context only
$200
minimum per work when the infringer proves innocent infringement
$750 to $30,000
the ordinary statutory range per work under 17 U.S.C. 504(c)
Up to $150,000
statutory maximum per work for willful infringement under 17 U.S.C. 504(c)

These are US Copyright Act statutory ranges, not predicted outcomes. Article 50 transparency obligations apply August 2, 2026 for new systems, December 2, 2026 for systems already on the market; whether they bear on a publisher workflow depends on the actor, use, and jurisdiction. Encypher provides technical infrastructure, not legal advice.

Setup

No engineering staff required

Solo newsletter writer or 800-person newsroom: setup takes under 20 minutes using any publishing platform.

  1. 01

    Sign up free. The free tier will always exist at $0.

  2. 02

    Copy your API key. It is waiting in your dashboard.

  3. 03

    Paste it into WordPress, Ghost, or your CMS settings. One-time configuration.

  4. 04

    Publish your next article. It is signed automatically.

CMS, SDK, and archive options
  • WordPress. Plugin, one-click activation

    Live
  • Ghost. Webhook integration, automatic signing on publish

    Live
  • Custom CMS or archive. Python, TypeScript, Go, and Rust SDKs; batch-sign your entire back catalog

    Live
  • Substack and Medium. Publishing integration

    Coming soon

Pricing

Start free. Add analytics when you need it.

Use free signing and verification to establish the record. Paid analytics adds external-domain detection; Meter is an early-partner program.

Start here$0 - free signing under fair-use guardrails and unlimited verification
  • Encypher patent-pending tech plus C2PA
  • RSL-compatible verification included
  • 100% of direct licensing revenue stays with the publisher
EnterpriseCustom - unlimited use and all add-ons
  • Exclusive capabilities included
  • Founding Coalition fee waived
  • You keep 100% of direct licensing revenue

Enterprise needs?

FAQ

Frequently asked questions