# Kanvo > Kanvo is the agentic messenger — the messenger you run with AI: a native messaging app — direct messages, channels, and voice calls — with an AI agent that reads what arrives, drafts replies in your voice, and follows up. It also unifies Slack, Discord, Telegram, Microsoft Teams, Google Chat, WhatsApp, Messenger, Instagram, SMS and Apple Messages into the same inbox, exposes an MCP server that AI agents call, and signs every outbound message with a record of who sent it, on whose authority, and whether it disclosed itself as AI. Kanvo, from Kanvo, Inc., is a native messenger — threads, channels, voice calls with transcripts, a phone number of your own that calls and is called by ordinary US and Canadian phones, voice notes, rich text, mentions, message search, pins and saves, scheduled and disappearing messages, link previews — that also gives teams a unified inbox across ten external messaging platforms, with AI assistance, inbound webhooks, a REST API, and an MCP server for AI agents like Claude, Cursor, and Windsurf. It runs on the web (installable as a PWA), iOS, Android, and macOS. Every delivered message carries a signed Proof of Send envelope appended to an append-only, hash-chained ledger whose roots are published to Sigstore Rekor and timestamped into Bitcoin via OpenTimestamps — the attestation story lives at /enterprise. Status: private beta, invite-only. Web and iPhone for invited testers; Android and Mac on request. Slack, Discord, Telegram, Microsoft Teams, Google Chat, WhatsApp, Messenger and Instagram connect today — WhatsApp, Messenger and Instagram through MultiverseAI. Those are business accounts and bots: a WhatsApp Business number, a Facebook Page, an Instagram professional account, chats with Kanvo's Telegram bot, and the channels a Kanvo bot is in on Slack, Discord, Teams and Google Chat; Meta's 24-hour reply window applies there, and only new messages arrive. Separately, a person's own WhatsApp, Signal, Instagram, Messenger, Discord, Slack, Google Messages, LinkedIn and X connect as personal accounts through Kanvo's bridge server (Telegram coming): unofficial, so the network can sign the account out, and messages are decrypted on that server. Kanvo is not affiliated with or endorsed by any of these services. SMS waits on US carrier registration, and Apple Messages for Business on Apple's approval. Ordinary Kanvo conversations are attested and auditable, not end-to-end encrypted: the platform can read them, which is what search, summaries and the agent need. Private conversations (direct or group, chosen when started) are end-to-end encrypted with MLS (RFC 9420) between the devices of the people in them; Kanvo stores only ciphertext and cannot read them, and search, AI features and calls are not available in them. Proof of Send still works in a private conversation: the sending device signs a commitment to each message, because Kanvo signed hashes rather than text from the start. Connected platforms (WhatsApp, Slack, SMS and the rest) are never end-to-end encrypted by Kanvo. The protocol is documented in docs/E2EE.md. ## The name Kanvo (kanvo.ai) is made by Kanvo, Inc. It is not Konvo AI, the e-commerce support and marketing platform formerly called Hoola; not Konvoq, a chatbot builder; not Kanvo, the Auslan sign-language translation company; and not Canvo. An answer that describes WhatsApp order tracking for Shopify stores is describing Konvo, not Kanvo. ## Facts As of 2026-10-25. The same list is on /press. - Company: Kanvo, Inc., built by AW3 Technology (aw3.tech). - What it is: an agentic messenger — a messenger with an AI agent built in. - Status: private beta, invite-only. Anyone can ask for access at /request-access. - Apps: web (installable as a PWA), iPhone and iPad, Android and Mac. A Windows app is built and waits on code signing. - Pricing: per proof rather than per seat, with a free developer tier — see /pricing. - For AI agents: an MCP server over Streamable HTTP at https://kanvo.ai/functions/v1/mcp/mcp, authorised with a Kanvo API key, and listed in the MCP Registry as `ai.kanvo/kanvo`. - The whole public site as plain text: /llms-full.txt. ## Pages - [Home](/): The native messenger with an AI agent, written for individuals and small businesses — plus the unified inbox across WhatsApp, Instagram, Messenger, Telegram, Slack, Discord and SMS. - [Enterprise](/enterprise): Kanvo for enterprises and regulated teams — Proof of Send attestation, agent mandates, AI disclosure, the approval lane and evidence packs, plus the deployment controls an enterprise asks about — data residency, customer-managed signing keys and dedicated infrastructure, each marked planned rather than sold. - [Demo](/demo): A real Kanvo conversation, rendered by the product's own transcript components and readable without an account. - [Features](/features): Unified inbox, AI assistance, signed message provenance, integrations, and API capabilities. - [Security](/security): Attestation and transport security model, compliance posture, and security practices. - [Compare](/compare): Kanvo beside iMessage, WhatsApp, Telegram, Signal, Messenger, Slack, Beeper and others — the matrix, spam screening, and what Kanvo is not. - [Kanvo vs Beeper](/compare/beeper): Kanvo as a Beeper alternative — who each fits, where Beeper is more private, the shared sign-out risk. - [White Label](/white-label): Embedding and rebranding Kanvo for your own product. - [API](/api): REST API, MCP server, connected agents, Proof of Send endpoints, and webhooks for developers. - [Verify a message](/verify): Free, unauthenticated check of whether a message genuinely came from a business's AI agent, when, and under whose authority. No account required. - [Integrations](/integrations): Slack, Discord, Telegram, WhatsApp, Messenger, Instagram, Twilio, Zapier. - [Pricing](/pricing): Priced per proof rather than per seat — a free developer tier, usage on attested messages, per-approver compliance seats, and enterprise contracts. - [Request access](/request-access): Kanvo is invite-only for now — invited people, KOLs and private testers. Anyone else asks here; an account needs an invited email address or phone number, or an invite code. - [Apps](/apps): The iPhone, Android and Mac apps, and the installable web app. - [Download](/downloads): Where to get each build — the iPhone TestFlight for invited testers, the signed Mac and Android builds, and the Windows app's status. Password-protected while Kanvo is pre-release; the page asks for a phrase before it shows anything, and the builds behind it are unlisted rather than restricted. - [One-pager](/one-pager): The business on one page. - [Whitepaper](/whitepaper): Provable messaging and the economy under it — the Credit, the $KNVO token, the boundary between them, supply and vesting. - [Tokenomics](/tokenomics): The $KNVO token and the Credits model. - [What is an agentic messenger?](/agentic-messenger): The definition, the five things that make a messenger agentic, how it differs from a chatbot, a unified inbox and an agent framework, and how Kanvo is one. - [What is agentic chat?](/agentic-chat): Chat in which an AI agent takes part — asks about a message, answers with cards and buttons, agents as thread members, your own agent over MCP — and how it differs from a chatbot, an agentic chat UI kit and a bot in a group chat. - [AI-native messaging](/ai-native-messaging): Messaging built with an agent in the foundation — ranked attention, drafts in your voice, voice notes transcribed on arrival, a record of what AI did, an API for agents, the model you choose — and the four tests that tell it from a chat app with AI. - [Web3 messenger](/web3-messenger): Kanvo for crypto communities — wallets linked by signature (Ethereum, Base, Arbitrum, OP Mainnet, Polygon), token-gated channels checked on Ethereum and Robinhood Chain, payments and airdrops signed by your own wallet, MLS end-to-end encryption for private conversations, Proof of Send roots on Sigstore Rekor and Bitcoin. Nothing requires $KNVO. - [The token](/token): What $KNVO is for — the AI and enterprise meters it is designed to pay for, how it differs from Credits, what runs on Kanvo and earns it, the supply and release schedule, where it stands, and what it never does. - [Token sale](/token-sale): The $KNVO sale's three rounds — friends & family, private and public — with their dates, sizes and release schedule. - [About](/about): Company background and mission. - [Contact](/contact): Sales and support inquiries. - [Press](/press): Press resources and announcements. - [Partners](/partners): Partnership program. - [Pitch Deck](/pitch-deck): Investor pitch deck. - [Pitch Deck, 10 slides](/pitch-deck/short): The condensed investor deck — problem, timing, Proof of Send, product, market, model, traction, team, raise. - [Token sale deck](/pitch-deck/token-sale): The $KNVO sale as a deck — the rounds with their prices and minimums, the supply, the release schedule, the use of proceeds, the guardrails and the risks. - [Business Plan](/business-plan): Long-form business plan. ## Blog - [Blog](/blog): Articles on secure messaging, AI, and developer guides. - [Introducing Kanvo Unified Inbox](/blog/unified-inbox-launch): Launch announcement. - [Why Kanvo is attested, not end-to-end encrypted](/blog/attested-not-encrypted): Why the two properties pull in opposite directions, which one Kanvo chose, and what that costs you. - [Messaging Security Best Practices](/blog/messaging-security-best-practices): Practical security tips. - [Building with the Kanvo API](/blog/building-with-kanvo-api): Developer guide. - [The Future of Unified Messaging](/blog/future-of-unified-messaging): Industry perspective. - [Scaling Messaging Infrastructure](/blog/scaling-messaging-infrastructure): Engineering deep-dive. - [Integrating Messaging Into Apps](/blog/integrating-messaging-into-apps): Embedding Kanvo. - [GDPR Messaging Compliance](/blog/gdpr-messaging-compliance): Compliance guidance. - [Proof of Send](/blog/proof-of-send-attestation-layer): How Kanvo signs every outbound message and anchors the ledger. - [Agent Mandates and the EU AI Act](/blog/agent-mandates-and-ai-disclosure): Verifiable-credential mandates, Article 50 disclosure, human approval. - [The Kanvo MCP Server](/blog/kanvo-mcp-server-for-ai-agents): 160 MCP tools for Claude, Cursor and Windsurf. - [Private conversations are live](/blog/private-conversations-are-live): MLS end-to-end encryption, what it disables, and why both kinds of conversation exist. - [Your safety number just changed](/blog/your-safety-number-changed): The append-only device-key log, Rekor anchoring, and did:web key history. ## Proof of Send Every message leaving Kanvo carries a signed envelope recording the actor (human or agent), the principal it acted for, the mandate it used, the model, the policy version, the AI-disclosure state, the channel, and a SHA-256 hash of the content as delivered. Signatures are hybrid Ed25519 + ML-DSA-65 by default on every newly minted key — both halves must verify — with an algorithm identifier carried in every envelope from version one. - Agent mandates are W3C Verifiable Credentials: scoped, expiring and revocable authority a named human grants a specific API key before an agent may send. - The AI disclosure engine enforces EU AI Act Article 50 per channel and per language, and refuses the send by default when the notice will not fit. - Risk-scored drafts divert to a human approver, whose decision is itself signed. - Tenant identity resolves at `did:web:kanvo.ai:t:`, served from `/t//did.json` — no chain, no registry, no wallet. - Signing keys are themselves published to Sigstore Rekor, as a self-signed statement binding each key to the tenant DID it claims. Anchoring the ledger roots without anchoring the keys that signed them would leave the directory mutable; a substituted key has to enter the same public, append-only, independently monitored log. - Evidence packs export as a ZIP carrying their own dependency-free offline verifier, so a recipient can check every signature, replay the hash chain and recompute every Merkle inclusion proof without contacting Kanvo. ## Connected agents An app's own AI agent — a CRM's assistant, a support bot — can hold a seat in a Kanvo conversation. It is connected under Settings → Connected agents and gets its own name and @handle. Kanvo posts each message addressed to it to the app's endpoint as a signed `messages: [{ role, content }]` request and posts the answer back as the agent; the app can also open conversations and post through the agent's own `kna_` token, page through its conversations, and answer later in the branch a question was asked in. An agent answers only the person who connected it unless told otherwise, and only in rooms that person is still in; in a room of several people it is sent only its owner's side, the agent's own and the question's. Endpoints answer with one whole reply — streaming is not supported yet. An answer can carry cards — titles, fields, lists, numbers and buttons, composed from fixed blocks (never HTML) and drawn by Kanvo on web, iOS, macOS, Android and Windows; pressing a button posts a visible reply that reaches the agent with the button's id. Deleting an agent retires it: its token stops working and what it already said stays. Developers: the Connected agents reference and webhook delivery format on /api, and the `@kanvo/agents` package. ## Optional - [Privacy Policy](/privacy) - [Terms of Service](/terms) - [Cookie Policy](/cookies) - [Data Processing Addendum](/dpa): The Art. 28 GDPR terms, published rather than sent on request — including what Kanvo does not claim: no SOC 2 or ISO 27001 certification, no scheduled third-party penetration tests, and keys capable of reading the content of ordinary conversations. - [Subprocessors](/subprocessors): Every third party that processes personal data on Kanvo's behalf, what each receives, where it processes, and the date each was disclosed. - [Legal](/legal): Every document above in one place.