YOUR INBOX. YOUR AGENT. YOUR WORLD.

Email for people,
agents, and what
comes next.

A familiar inbox for you. A real email address for your agent. One mail service, with the web, REST, and MCP built around it.

Create your inbox Give your agent an inbox

Start with a KeyKeeper address. No card needed to create an inbox.

YOUR WORLD, IN ONE INBOX01 / MAIL

FROM YOUR AGENT[email protected]

RESEARCH COMPLETE

The next step is in your inbox.

I found the three options you asked for.
Here’s the comparison, ready when you are.

GET /api/v1/agent/inbox

{ "folder": "INBOX", "totalMessages": 1 }

Illustrative message · one inbox, multiple interfaces

Human web inboxReal agent mailboxesREST + MCPOwned mail infrastructure

ONE SERVICE. THREE WAYS IN.

Email that meets you
where you work.

Use it yourself, let your agent operate its own mailbox, or build on the API.

01 / PEOPLE

A quieter place for mail.

Read, compose, reply, and keep your sent messages together. A lightweight inbox with two-factor authentication and optional OpenPGP bodies.

Meet your inbox →

02 / AGENTS

An address of their own.

Provision a real mailbox with one request. Receive messages, read attachments, and connect through REST or MCP using an API key.

Start with an agent inbox →

03 / DEVELOPERS

Mail you can build on.

A shared sending API with credit accounting and safe retries. We’re preparing the delivery controls and custom domains for a small transactional email pilot.

Explore the developer path →

AGENT-FIRST, HUMAN-READABLE

A real inbox.
One request away.

Your agent gets an address and a secret API key. Send a message to that address, then let it read the inbox with its key.

Create the mailboxRegister with an agent ID. Save the returned key.
Receive your first messageSend to the new address from a mailbox you control.
Read through REST or MCPFetch messages and attachments from the same inbox.

Read the complete quickstart →

Create a real mailbox

curl --fail-with-body https://keykeeper.world/api/v1/agent/register \
  -H 'Content-Type: application/json' \
  -H 'User-Agent: MyAgent/1.0' \
  -d '{"agentId":"my-agent","name":"My agent"}'

Receiving is available now. New agents start with zero sending credits, and funding is paused. See current availability.

A CLEARER KIND OF TRUST

Your mail deserves
plain answers.

KeyKeeper runs on an owned mail stack. We’ll tell you what’s protected, what the service can access, and what’s still being built.

Privacy details →What works today →

Verified connections

Mail connections use verified TLS. Accounts support two-factor authentication and one-use backup codes.

Optional OpenPGP

Encrypt supported message bodies with saved recipient keys. Standard email and metadata remain accessible to the service.

Keys belong in your vault

New agent API keys are stored as hashes. Save yours when you create the mailbox; it cannot be retrieved later.

A wider Key* world

Mail is the starting point for connected identity and agent services. Shared scopes and custom domains are next.

START WITH A CONVERSATION

Your next collaborator
could use an inbox.

Build something useful with the mail service that’s already here.

Create an agent inbox ↗Create a human inbox

Email for people,agents, and whatcomes next.