Mark every completed AI output. Keep the evidence.

The coalition is a commercial program for publishers and AI companies that want common machine-readable terms and a shared contracting path. Coverage, participating sources, and whether future members are included depend on the agreement you sign. Custom bilateral terms can still sit alongside it.

An evidence package records what a signing workflow supplied, such as signer identity, timestamp, rights terms, and integrity data. A document-level C2PA signature can be checked with standards-based tools. Encypher sentence-level text markers use a separate resolver layer and are not independent sentence claims inside the C2PA manifest.

For content you ingest, verification can show whether supported provenance is present and return its recorded terms before a dispute exists. A verification log documents the check your system made. Pipeline-wide retrieval and outcome instrumentation is part of the early integration partner program.

If a coalition publisher raises a dispute, the signed commercial agreement defines the resolution process and the content it covers. The evidence package supports that process; it does not settle a copyright or licensing dispute by itself.

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 white-label identity 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. A license can reduce uncertainty about the covered content and create a documented commercial basis for its use, but it does not answer every copyright, privacy, or data-governance question. Counsel should assess the relevant sources, uses, and jurisdictions. Encypher provides the provenance and usage records that support that review.

robots.txt and noai directives apply at crawl time on the publisher’s server. Provenance is attached to a particular signed version of the content and can travel with copies that preserve its C2PA manifest or Encypher text markers. Signing an archive later establishes a new record; it does not retroactively change or license copies already held elsewhere.

Encypher is not an enforcement mechanism. It makes provenance and supplied licensing terms machine-readable and verifiable. robots.txt is a crawl signal; content provenance can remain available after publication when the relevant metadata or markers survive the content path.

For sources that carry Encypher rights terms, yes. Each signed source projects to a W3C ODRL policy bound at signing time, and a deterministic engine evaluates that policy against the intended use you name. The same inputs return the same verdict every time: a prohibition outranks a permission, and a request that matches no rule defaults to deny.

The verdict is advisory and machine-readable. Encypher returns permit or prohibit together with the rule that decided it, and your own retrieval or generation layer decides what to do with the answer. Encypher does not sit in your request path. Where a permit depends on a commercial license, that is a licensing outcome recorded beside the verdict, not a third ODRL decision.

A verdict is only as good as the record behind it. It reflects the terms the signer supplied and bound to the content; it does not establish ownership or settle a dispute.

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, a standard document-level C2PA signature can be verified locally with open-source tools. Resolving Encypher sentence-level text markers requires the matching verification record; enterprise customers can discuss a customer-hosted deployment for that layer.

Encypher’s output marking is designed to support Article 50 transparency workflows, with marking obligations applying August 2, 2026 for new systems and December 2, 2026 for systems already on the market. A successful sign operation can record the supplied AI-generation metadata in a C2PA manifest and add supported text markers. Whether that satisfies the law depends on the content, system, deployment, and final implementing rules.

We are not a law firm. Confirm the implementation with counsel in each jurisdiction; we can provide technical documentation for that review. Separate configurations may support other marking regimes, but one implementation should not be assumed to satisfy every mandate.

You can verify signed content from publishers outside the coalition. C2PA is an open standard, and Encypher can validate supported C2PA manifests regardless of coalition membership. Attribution is only as strong as the signer identity, certificate chain, and metadata in that record.

When supported provenance is absent, verification returns a not-found or unverified result rather than proof that the content was never signed. Coalition membership adds a contractual layer; it is separate from technical provenance verification.