Skip to main content
Programmatic

Verified Inventory,
Priced Like It

Cryptographic provenance signals in the bid stream that buyers can check themselves. Sign your content (free), from news and blogs to video and CTV, and that proof rides the ad auction: sellers label verified inventory, buyers bid on it with evidence instead of vendor scores.

Talk to Partnerships All Partner Tracks

One Signal, Two Sides of the Trade

The same provenance signal serves whoever is reading it: supply labels what is verifiably real, and demand prices it with proof in hand.

Sell Side: Publishers and SSPs

Label what is real, and let the market see it

Sign your pages, articles, videos, and CTV streams once (free) and they carry cryptographic proof of who published them. Encypher puts that proof into every bid request, so your inventory is distinguishable from unsigned pages and AI-generated content farms without buyers having to take your word for it.

  • Signing is free for publishers, so labeling costs your supply nothing
  • One-line config in an existing Prebid setup, no new ad-stack plumbing
  • Provenance-signed inventory is labeled in the bid request itself
  • Differentiate from AI slop with cryptographic proof, not assertions
  • A signal buyers can factor into pricing decisions on verified supply

Buy Side: DSPs and Brands

Bid on provably human, provenance-signed pages

The trust signal arrives inside the OpenRTB bid request you already process. Every field is documented, and the proof behind it is independently checkable against the official C2PA trust list. Brand safety backed by cryptography, not a vendor score you cannot audit.

  • A documented signal set in the bid request, not a black box
  • Trust status derived from real certificate chain validation
  • Signer identity surfaces only when chain validation passes
  • Declared AI or human provenance relayed verbatim, no guesswork detection
  • Check any manifest yourself: the proof does not require trusting Encypher

What You Can Integrate Today

The signal surface below is live. Everything further out is labeled for what it is.

Live today

Prebid RTD module

A Prebid Real-Time Data module reads the provenance signal on the page and injects Encypher trust signals into the OpenRTB bid request, where SSPs and DSPs read them like any other bid-stream field.

OpenRTB trust-schema declarations

Every field in the site.ext.data.c2pa extension is documented with exact definitions and versioned, so new fields are additive and safely ignorable by consumers that do not read them.

Signed signal endpoints

Public signing and manifest endpoints back the module. Page content is signed as a C2PA manifest, and every manifest is retrievable and independently verifiable by any party in the chain.

In pilot and on the roadmap

Paid signal layer

In pilot with early partners

Licensed, server-side domain-level intelligence for the demand side, delivered through authenticated partner keys. The free bid-stream facts stay free; derived intelligence is the licensed layer.

Metering-based settlement

In pilot with early partners

Impression measurement instrumentation feeding contract-level reconciliation, so partner settlement can be grounded in co-measured counts rather than one-sided reporting.

AdCP alignment

Standards engagement

Aligning the signal schema with emerging agentic ad protocols including AdCP, so provenance signals stay portable as the ecosystem evolves. See the note below.

Agentic Ad Protocols

We are aligning our signal schema with emerging agentic ad protocols including AdCP. The bid-stream payload carries a verifier attribution field so any consumer, human or agentic, can see who emitted the signal and check it independently. This is standards engagement, not an exclusive integration: the goal is that provenance signals stay portable across whatever protocols the programmatic ecosystem settles on.

For Technical Readers: The Signal, Under the Hood

What the RTD module actually does on the page, and the exact shape it injects into the bid request.

What the RTD module injects

The module resolves a provenance payload for the current page and writes it to the OpenRTB bid request at site.ext.data.c2pa, where Prebid merges it into the request every bidder receives. It reads from three sources, in order:

  • Production path: the page carries a manifest meta tag placed upstream by a CMS plugin, CDN worker, or direct API integration. The module reads it with no signing call in the auction hot path.
  • Cache path: a local cache serves repeat pageviews without any network call.
  • Onboarding path: with no upstream signing in place, the module can sign page content once via the public signing endpoint, so a publisher sees the signal in bid requests immediately.

Every path and every error branch is fail-open: the module completes the auction callback whether or not a signal was resolved, so it never blocks or delays bidding. Full endpoint reference in the API documentation.

The OpenRTB extension shape

"site": { "ext": { "data": { "c2pa": {
  "manifest_url": "https://api.encypher.com/...",
  "verified": true,
  "trust_status": "trusted",
  "signer_name": "Example Daily News",
  "content_declaration": "human_declared",
  "verifier": "encypher.com",
  "schema_version": 4
} } } }

Shown abridged. The payload also carries signing metadata: signer_tier, signed_at, verified_at, content_hash, source, extraction_method, and action.

  • trust_status trusted, untrusted, or unknown. "trusted" means the signing certificate chain-validated against the official C2PA trust list, including EKU and revocation checks. Registration or payment status never influences it.
  • signer_name The publisher display name, present only when trust_status is trusted. An unvalidated certificate can never surface a brand-like name in the auction.
  • content_declaration human_declared, ai_assisted_declared, ai_generated_declared, or undeclared. A verbatim relay of what the signed manifest declares via C2PA actions and IPTC digitalSourceType. Encypher runs no AI detection; a manifest that declares nothing is undeclared.
  • verifier Attribution of who computed the signal (encypher.com), so consumers know which verifier emitted it and can hold that verifier to its published definitions.
  • schema_version Versioned payload. Fields are additive only; a consumer built against an earlier version keeps working and can ignore fields it does not read.

Standards, for the diligence file: Encypher is C2PA conformant and trusted in all four program categories: Generator, Validator, Certificate Authority, and Time Stamp Authority (passed June 30, 2026). Encypher authored Section A.7 of the C2PA specification and co-chairs the Text Provenance Task Force. Details on the trust page.

Bring Verified Inventory to Your Pipes

Tell us which side of the auction you operate on and what you trade. We will come back with the integration path and terms that fit.

Talk to Partnerships Contact Us