Help make permission a verifiable part of email.

XCIM is inviting ESPs, mailbox providers, ISPs, security platforms and infrastructure teams to implement, test and shape a portable permission signal for email.

Latest specification · draft-saez-xcim-04

Experimental individual Internet-Draft. A bounded C01/SR01 testnet pilot verified consent reuse and revocation on 26 October 2026; production readiness remains open.

Review the corrected consent model before beginning a new integration. The earlier programs and implementation evidence below remain historical; they do not establish conformance to the corrected revision.

Early Partners cohort

For ESPs and ISPs ready to adopt XCIM. We pair a sending team with a receiving team for a focused, non-production integration window. Partners get the public schemas, deterministic vectors, local runners, Emabled sandbox and technical office hours. In return, each partner names an owner, tests in shadow mode and shares a dated implementation report with sanitized evidence. Recognition is opt-in and earned by the evidence, not by payment or logo placement.

Start with a managed company or ESP pilot

Emabled now provides separate company and ESP workspaces. A company configures its application, consent manifest and sending domain, then authorizes an ESP for a specific scope. The ESP can evaluate JSON jobs or CSV/ZIP console uploads and download results. MFA and revocable authorization protect the ESP workflow.

The MuMaps managed pilot exercised Google registration, optional consent, signed receipts, list evaluation and revocation. It gives new partners a reproducible integration path; independent public verification and a paired sender/receiver test remain open gates.

Participation tracks

Track Who it is for First integration
Sending ESPs, CRMs, marketing and transactional email providers Start with authorized list evaluation and revocation handling in Emabled, under the corrected consent scope. Earlier XCIM-Reference and XCIM-Proof header adapters are historical experiments, not core requirements.
Receiving Mailbox providers, ISPs, secure email gateways and filters Parse and verify XCIM in shadow mode without changing delivery decisions.
Infrastructure Security, identity, observability, SDK and research teams Build resolvers, adapters, tooling, test fixtures or independent issuer implementations.
Identity Evidence Identity, browser, account-authority and verification teams Prototype an EVP-01 experimental adapter or OIDC-01 adapter for an XCIM Consent Issuer. Identity evidence is an input, never the permission decision itself.

What participants receive

What we ask

From interest to interoperability

01ExploringRead the docs and attend a technical introduction.
02BuildingIntegrate a sender, receiver or tooling surface.
03Self-testedRun the versioned checks against local fixtures.
04Interop-testedTest against Emabled and an independent implementation.
05Founding ImplementerPublish a dated implementation report.
Current maturity: XCIM v0.1 is a draft. The Emabled reference issuer has a verified managed pilot, but this program is not a certification scheme and does not grant a production trust mark.

Evidence and recognition

A profile experiment is not an interoperability result. Public status names the exact role, profile, implementation version, test date and limitations. LMGram Partners, when listed, is an external EVP verifier experiment in progress; it is not an XCIM Consent Issuer and is not treated as proof of XCIM interoperability.

Program safeguards

Protocol material remains publicly reviewable. Recognition is evidence- based and versioned, not pay-to-play. Emabled is a managed reference issuer, not the only issuer XCIM is designed to support. Delivery, filtering, abuse and trust decisions remain local to each receiver.

Read the governance process, inspect the tool inventory and review the operational interop surface ↗.