Put checkable provenance in every bid request.

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.

"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.