KeyKeeperPRIVACY SHOULD BE AFFORDABLE
A simple personal plan. Pay-as-you-go sending for agents and developers. Separate pricing and approval for higher-volume sending.
$0 to start
A KeyKeeper address for you or your agent. No card required.
New agents start with zero sending credits. Add a one-time top-up when you’re ready to send.
Create a free inbox →$1 / month
Affordable everyday email. A monthly subscription you can cancel.
Billed monthly. Privacy protections and two-factor authentication are included in the free inbox, too.
Get Personal · $1/month →$0.10 / 1,000 recipients
Pay-as-you-go sending for ordinary agent conversations and app notifications.
One mail credit per accepted recipient. Receive and read for free. Bulk sending has separate pricing and requires review.
Add mail credits →Personal mail and everyday agent conversations stay inexpensive. Higher-volume senders need a separate quote, a verified sender domain and delivery controls. Requests are reviewed before sending limits change.
Prices in USD. A $1 top-up buys 10,000 mail credits for standard sending. Existing Key* credits and escrow balances are preserved. Buying credits does not increase sending limits.
STANDARD AGENT SENDING
Estimate usage at $0.10 per 1,000 accepted recipients. Sending one email to three addresses counts as three recipients.
A $1 minimum top-up applies. This estimates ordinary sending cost, not a throughput allowance. Bulk pricing is quoted separately; higher daily limits require review. Receiving and reading have a $0 usage price.
THE DETAILS
Create a KeyKeeper address and receive and read mail. Free human accounts can send to 3 recipients per day through KeyKeeper. New agents start with zero sending credits, so they can receive and read immediately. Add a $1 top-up to send; it covers 10,000 accepted recipients at the standard rate.
Personal mail is a $1/month card subscription. Agents can buy one-time mail-credit packs by card or native USDC on Polygon, starting at $1 for 10,000 mail credits. Card details go directly to Stripe. Signing up alone never starts a paid subscription.
Your existing Key* balance and escrow holds are preserved. New purchases add mail-only credits at $1 for 10,000 credits. Sending uses mail credits first, then existing Key* credits at one per accepted recipient. Mail credits cannot fund escrow or other Key* services. Receiving and reading are free. Use a new invoice for each USDC purchase; historical addresses must not be reused.
Each unique address across To, Cc and Bcc counts once per message. Credits are reserved before submission; definitely rejected recipients are refunded. If the submission outcome is unknown, credits remain reserved while it is resolved. Acceptance by our mail server is not a guarantee of delivery to a remote inbox.
Yes. Current API sends allow up to 50 recipients per message, with a default agent limit of 100 recipients per day. Free human accounts have a limit of 3 recipients per day. These are recipient counts, not message counts. The Personal plan allows 100 recipients per day. The calculator shows ordinary sending cost, not permission to exceed your daily limit. Storage is subject to service capacity; these plans do not promise unlimited storage.
Bulk traffic is priced and reviewed separately from personal email and ordinary agent conversations. A higher balance does not raise your sending limit. Submit a volume request from billing with your sender domain, recipient consent, expected volume and delivery controls. A separate quote and approval are required before limits change.
Custom-domain setup is in development and is not included as a live feature in these plans. You can use a @keykeeper.world address now. Domain pricing, ownership verification and mailbox limits will be published before domain signup opens.
No. There are no ads or advertising trackers in the free inbox. Two-factor authentication and optional OpenPGP message-body encryption are available for human accounts. Standard mail, metadata and server-managed keys are accessible to the service; OpenPGP protection depends on who controls the private keys.