XCIM / Implementers

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.

Start in shadow mode. Validate against real integration patterns. Help resolve the protocol's open questions before v0.1 is frozen.

Join the Implementers Program Explore tools and access Use the Early Partner intake template View interop status ↗

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.

Three ways to participate

Track	Who it is for	First integration
Sending	ESPs, CRMs, marketing and transactional email providers	Generate `XCIM-Reference` and `XCIM-Proof`, publish manifests and consume revocation events.
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.

What participants receive

Versioned protocol material, implementation notes and open issue context.
Access to the Emabled reference sandbox for non-production testing.
Sanitized examples, public signing keys, draft schemas and deterministic conformance vectors.
Technical office hours and paired interoperability testing.
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

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 sandbox is operational, but this program is not a certification scheme and does not grant a production trust mark.

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