No. The Encypher publisher coalition operates as a network license: one agreement with Encypher covers access to all coalition members at the tiers each publisher has set (Bronze, Silver, Gold). You never negotiate directly with individual publishers unless you want a custom bilateral arrangement on top of the network agreement. As new publishers join the coalition, your license extends to them automatically.

An evidence package is a bundle of cryptographic proof about a piece of signed content: when it was published, who signed it, and which machine-readable licensing tier travels with it. The proof is embedded in the content itself and verifies against the publisher’s own key, so it is independently verifiable and does not depend on trusting Encypher’s servers.

For content you ingest, that same proof works in your favor. Verifying a source is a free API call today, and it tells you whether the content carries provenance and what license terms are attached, before any dispute exists. Your verification log then documents that you checked. Wiring those checks into a pipeline at ingestion scale is what our early integration partner program covers.

If a coalition publisher raises a dispute over specific content, the coalition licensing agreement is the resolution path: the same agreement that licenses the corpus going forward resolves questions about content already ingested.

Only if you put it in the blocking path, and you do not have to. Sign and verify are standard HTTPS API calls designed to run asynchronously: you return the model response to your user first, then sign or verify out of band and record the result. Nothing in the integration requires a synchronous call before your response goes out.

We do not publish latency benchmarks, so we will not quote numbers here. What is documented: batch endpoints accept up to 10,000 documents per request for archive and pipeline workloads, rate limits are 1,000 requests per minute on Growth and 10,000 per minute on Enterprise, and enterprise deployments support BYOK and on-premises options when verification needs to run inside your own infrastructure. C2PA is an open standard, so the verification logic can also run locally against open-source libraries with no network call at all. For inference-scale volumes, talk to us about an async batch architecture review.

The legal landscape is unsettled and active litigation is ongoing. Licensing is defensible regardless of how copyright law evolves: it removes the question entirely. More practically, enterprise customers are now asking about content provenance in security questionnaires. AI companies that can prove they license their content close deals that competitors cannot. Legal protection and competitive advantage are both real; the legal exemption argument only addresses the first.

robots.txt and noai directives apply at crawl time, on the publisher’s server. C2PA provenance is embedded in the content itself: it travels with the text wherever it goes, including content that was already in your training corpus before any crawl directive existed. A publisher who signs their archive retroactively attaches licensing terms to every copy of that content, on any server.

Encypher is not an enforcement mechanism. It is infrastructure that makes licensing terms machine-readable and verifiable. robots.txt is the crawl signal; C2PA is the content-level signal. Both have a role, but only C2PA works after the content has already left the publisher’s server.

For verification calls: we receive the text submitted for verification and return provenance metadata. We do not train on your data, do not retain content beyond the verification transaction, and offer a standard data processing agreement at enterprise tier.

For performance intelligence (an early integration partner capability): we record that a provenance check occurred, the result (verified / not found), and the timestamp. We do not store the full content of your AI-generated outputs unless you opt into spread analytics, which requires explicit configuration.

For the highest isolation: C2PA verification is an open standard and the verification logic can run entirely within your infrastructure using the open-source C2PA libraries, so no content leaves your environment.

Encypher’s output watermarking is designed to support Article 50 transparency obligations: the requirement that AI-generated content be detectable as such. The C2PA manifest embedded in each output identifies it as AI-generated, records the generation timestamp, and links to the source model. That is the technical requirement as written, with marking obligations applying from August 2, 2026 for new systems and December 2, 2026 for systems already on the market.

We are not a law firm and regulations are still being interpreted. Confirm with your counsel that our implementation satisfies your specific obligations in the jurisdictions where you operate; we can provide technical documentation to support that review. The China watermarking mandate is covered by the same integration under a separate configuration flag.

You can still verify content from publishers who have signed their content independently. C2PA is an open standard and any publisher can embed provenance metadata using it. If the content carries a valid C2PA manifest, Encypher can verify it and attribute it to the source, regardless of coalition membership.

For content without any C2PA watermark, verification returns "unsigned", which is itself a signal. Coalition membership adds the licensing agreement layer; the provenance verification layer works on any signed content.