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
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
- Versioned protocol material, implementation notes and open issue context.
- Reviewed access to company and ESP workspaces for a managed pilot, including scoped list authorization, CSV/ZIP evaluation and exports.
- Sanitized examples, public signing keys, draft schemas and deterministic conformance vectors.
- Technical office hours and paired interoperability testing.
- Identity Evidence profile notes, negative cases and a path to test EVP-01 without claiming production support.
- Opt-in public recognition tied to a specific version and test result.
What we ask
- A named technical owner and one test environment.
- A small integration commitment over an 8–10 week cohort.
- Feedback on ambiguity, failure behavior, privacy and operational cost.
- No customer PII in test artifacts, logs or issue reports.
- Permission before publishing your name, product or implementation report.
From interest to interoperability
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 ↗.