XCIM consent infrastructure

Permission that can travel with the person.

Emabled gives issuers, vendors, and providers a shared way to request consent, issue receipts, and verify the lifecycle of a permission.

XCIM 0.1 · signed receipts · revocable by design
LIVE PROTOCOL FLOWVERIFIED
01
Consent requestedVendor → person
02
Identity confirmedProvider assertion
03
Receipt issuedSigned + auditable
transparency frontier0x7a…e91
Built for the whole consent chain

Clear signals. Durable proof.

Consent is not a checkbox. It is an event with an issuer, a subject, a scope, and a lifecycle that deserves to be observable.

01

Ask once.
Prove it later.

Hosted consent and provider adapters turn an intent into a portable, signed receipt.

See the console →
02

Trust with
receipts.

Receipts, revocations, and transparency batches make every decision inspectable.

Read the docs →
03

Designed for
your stack.

Use an API, SDK, or a hosted surface. XCIM keeps the contract stable underneath.

Build on XCIM →

For developers

Your integration should feel like a clean handoff.

Request consent from your product, receive a receipt you can verify, and subscribe to lifecycle events without owning the identity layer.

Create a workspace
// create a consent session
POST /v1/consent-sessions
{
  "manifest_uri": "xcim://…",
  "return_uri": "https://app.example/callback"
}

// verify the receipt later
GET /v1/receipts/rc_…

Open by default

Every important event has a place in the record.