EVP
Verify control of an email identity through the provider and browser, then bind that evidence to an explicit XCIM decision.
Provider-backed evidenceEVP + OAuth identity evidence - XCIM consent infrastructure
Emabled connects provider-backed EVP and OAuth identity signals to an explicit XCIM consent flow, then issues signed, revocable receipts your product can verify.
0x7a…e91EVP and OAuth answer who is present. XCIM answers what they agreed to. Emabled keeps those jobs separate so every permission remains clear, portable, and auditable.
Identity evidence, your way
Use provider-backed EVP when browser support is available. Keep your existing OAuth integration as a dependable path for every other user, without changing the consent contract underneath.
Verify provider-backed identity with EVP or OAuth while keeping provider tokens out of your receipt layer.
Compare identity paths →Hosted XCIM consent turns an explicit choice into signed, revocable, queryable evidence.
Read the trust model →Use an API, SDK, or hosted surface across multiple sites while the XCIM contract stays stable underneath.
Build with Emabled →For product teams
Connect your current OAuth flow or opt into EVP where supported. Emabled routes the user through explicit XCIM consent and returns a verifiable receipt without asking you to build an identity layer from scratch.
Create a workspace// create a consent session POST /v1/consent-sessions { "manifest_uri": "xcim://…", "return_uri": "https://app.example/callback", "identity_profiles": ["evp-01", "oidc-01"] } // verify the receipt later GET /v1/receipts/rc_…
Open by default