Verified identity in AI chat
When users interact or transact inside an AI chat, you need to know who they are. Proofenance gives you verified identity in that context: our MCP server verifies users in the conversation and issues a signed identity token your backend can validate.
Proofenance Agentic Identity: identity in the chat
We provide an MCP server that your AI agent or chat product connects to. From the same conversation, you trigger verification (email, phone, optional document). The user may be directed outside the chat for some steps (e.g. email link, document upload in browser). They are redirected back to the chat after completing the flow, or can complete verification asynchronously. Email: the user clicks a link and is redirected back to the chat after verification. Phone: they tap a link in SMS or enter the code in the chat (e.g. via "insert from SMS" on devices). Documents: they upload in the browser for accuracy and to avoid AI mishaps, then return to the chat. All steps can be done async; the same personId is persisted, and if you request identity later after they've added more info, we return an updated token. You receive a signed identity JWT that you validate with our JWKS. No separate identity portal: verification is tied to the chat context (same session, same personId). That’s our product for agentic AI and ecommerce.
Setup and integration guideVerified identity in the conversation
Our MCP server (Proofenance Agentic Identity) verifies users inside the chat via email, phone, and optional document checks. You get a signed identity token so you know who you're dealing with.
Bot-proof by design
Verification requires real data: email confirmation, phone ownership, or document checks. Bots and throwaway accounts can't pass.
Built for agentic AI
MCP integration, JWKS-validated tokens, and APIs that fit into your agent pipeline. Users may be directed outside the chat for some steps (e.g. email link, document upload) but are redirected back to the chat after the flow or can complete verification asynchronously.
Who it’s for
AI chat and agentic commerce
You’re building or using AI chat for sales, support, or transactions. You need to verify the user in that same flow. Our MCP server and identity token give you the verified user; you decide how to use it (e.g. gating actions, compliance, personalization).
Regulated and high-value sectors
Art, luxury, financial services, or any sector where you must know who the user is. We give you a compliant, auditable way to verify identity in the chat via MCP and a JWKS-validated token.
Verified identity in your AI chat
Connect your agent to our MCP server and start verifying users in the conversation.