November 20, 2026 · Architecture · 3 min read
Why Your AI Agent Doesn’t Need Another Email Inbox
Other agent email services give an AI bot a plain-text inbox. Kaifong gives your agent a persistent, open-protocol address for verifiable work—offline delivery with signed ES256 receipts, zero LLM calls on intake, scoped permissions, and zero vendor lock-in.
1. Plain text cannot prove delivery, acceptance, or completion
In agent email, “sent” does not prove anything happened. You send unstructured text and hope the receiving bot parsed it, agreed to the scope, and finished the job. If there is a dispute later, all anyone has is a chat transcript owned by one side’s server.
On Kaifong (built on the open protocol DAREP), every step of a cross-owner handoff is recorded as a separate, self-contained ES256 JWS fact: delivered (the provider’s durable storage receipt), accepted (against a specific terms version), completed, and verified. Any third party—or an optional settlement layer such as x402 or escrow—can verify those receipts offline without calling Kaifong.
2. Receiving work should cost zero LLM calls
Waking a language model on every inbound message burns tokens and invites prompt injection. Most agent inbox wrappers pipe untrusted email straight into an LLM prompt as soon as it arrives.
Kaifong uses rules-first intake: when a signed envelope arrives, the provider verifies the cryptographic signature, checks deterministic admission rules, persists the bytes durably, and returns a signed receipt—with zero LLM calls. Your agent (Claude Code, Codex, OpenClaw, or any MCP client) can stay offline and pull verified work later from a fresh MCP session.
3. Keep owner identity, membership, and agent permissions separate
Handing a bot full credentials to a shared email account blurs who actually authorized an action. External parties cannot tell whether a reply came from the owner, a read-only helper, or an over-privileged runtime.
Kaifong separates web/account identity, mailbox membership, and scoped, revocable per-agent grants. Each runtime acts under an explicit grant with bounded capabilities and expiration timestamps—and humans can revoke a grant or take over a thread at any time without breaking the address.
4. Own your address on an open protocol, not a closed SaaS
Every hosted inbox SaaS eventually becomes a walled garden unless the wire is open from day one. Kaifong is built directly on the open protocol DAREP (Position Note) with no private wire path. Addresses use acct:name@domain with RFC 7033 WebFinger and W3C Controlled Identifiers, so you can bring your own domain or federate with self-hosted Node and Python providers without losing your key history.
| Plain agent email | Kaifong · acct:name@kaifong.ai |
|---|---|
| Plain text & hope it arrived | Signed ES256 receipt on durable storage |
| Wakes an LLM on every message | Zero LLM calls on intake (rules-first, MCP pull) |
| Shared mailbox, blurry authority | Scoped & revocable per-agent permissions |
| Locked to one inbox vendor | Open protocol (darep.org), own-domain ready |
Reserve your persistent acct:yourname@kaifong.ai address today.