Agents and wallets, in full

Kanvo is a messenger first. Underneath it are two things a messenger does not usually have: somewhere an AI agent can work under authority you granted it, and somewhere a wallet counts as identity.

An agent can hold a seat here

Kanvo reads and drafts for you. It also gives your own AI a scoped, revocable place to work — and signs what it sends, so you can prove afterwards what it did.

Ask Kanvo, across the whole workspace

Who has been waiting longest, what you agreed back in March, what still needs an answer. It reads through your own session, so it sees what you see and nothing more — and holds no tool that can send or delete.

Bring your own agent, over MCP

160 tools over Streamable HTTP: contacts, conversations, messages, search, billing and the proof ledger. Point Claude, Cursor or anything else that speaks MCP at an API key — which never even sees the tools its scopes leave out, rather than being refused them.

Authority it is granted, not authority it assumes

A named person issues a mandate before an agent may send: which channels, which contacts, how many a day, when it expires. A signed W3C Verifiable Credential, withdrawable at once — and issuing one takes a human session, so no agent can widen its own.

A person on the ones that matter

Drafts touching a new contact, money, or the edge of a mandate stop for approval instead of going to the wire. The decision is itself signed into the message's record, so “a person reviewed this” is evidence rather than an editable row.

It tells people it is an agent

AI-originated messages disclose themselves, per channel and per language, as Article 50 of the EU AI Act requires. Where a channel cannot carry the notice, the send is refused rather than delivered quietly without one.

Bring a wallet. Keep your keys.

An address you have proved is a way to sign in, a thing a room can be gated on, and a way to be paid. Kanvo operates no chain, holds no keys and takes custody of nothing.

Sign in by signing

No password and no email round trip — sign the challenge and you are in. A wallet Kanvo has never seen becomes an account, rather than a feature only existing customers can use.

Rooms gated on what somebody holds

A channel can require an ERC-20 or NFT balance on Ethereum, Base or Robinhood Chain — including Robinhood's tokenized stocks, so a room can be for holders of 1 AAPL — or a balance of Kanvo Credits, checked as someone joins. Balances sum across every wallet you have proved rather than the largest one — and when a node…

Payment inside the thread

Send on Ethereum, Base, Arbitrum, Optimism or Polygon without leaving the conversation. Your wallet signs and broadcasts; Kanvo shows a form and keeps a record. The last screen names the network in words and never shortens the address, because a shortened address is exactly what address poisoning relies on.

Airdrop back to the room

A channel owner can send the gate token to members from their own wallet: approve once, then disperse in batches. Kanvo builds the list and records what the wallet reported. The funds never pass through it.

A record that does not rest on trusting us

Every message leaves with a signed envelope, hash-chained per account, and the roots go hourly to Sigstore Rekor and into Bitcoin through OpenTimestamps — signing keys with them, so a substituted key must appear in the same public log. Your account also resolves as a did:web document, with any linked wallet published…