Now: private pilot
Live
- yourname@franked.email addresses delivering to an existing inbox
- Holds for unknown senders, with payment links sent only to authenticated senders
- Card deposits, one-click refunds, automatic donation of unanswered deposits
- Allowlists for addresses and whole domains, and a dashboard to manage everything
- Silent holds for bulk and automated mail
Next: a better email product
In development
- Reaching senders with imperfect email setups. Many legitimate small senders don't publish DMARC. Franked will still notify them when their mail passes basic sender checks.
- Sender credit. Prepaid balances for repeat senders, which make small deposits economical and refunds instant.
- Proof of a human at send time. A discount or waiver when the sender confirms each message with a passkey, so a person pressed send.
- Public charity ledger on franked.org, with totals and receipts.
- Native aliases for your own domain. Protect addresses like contact@yourcompany.com directly, with ownership verified. How custom domains work.
- Filtering inside Gmail and Outlook, so recipients can keep their existing address.
Later: payments for AI agents
Planned
- Agents pay deposits inside the HTTP request using the x402 standard (HTTP 402 Payment Required), with stablecoin settlement making cent-level prices practical.
- Payment links already return machine-readable terms to non-browser clients, so agent support is additive, not a redesign.
- Agents are welcome. Breadth is what costs money: one targeted message is cheap, fifty thousand are not.
Beyond email: verification walls for every inbound channel
Exploring, at franked.dev
- Franked for Forms. A drop-in endpoint and widget that puts a refundable deposit or a proof of human in front of contact, quote and demo forms.
- Franked for Support. Priority lanes for verified or paying requesters, so real customers aren't buried under automated tickets.
- Built on the gateways, not against them. For APIs, datasets and content, Cloudflare's Monetization Gateway and Amazon CloudFront's x402 integration already let site owners charge automated callers per request. Franked interoperates with both instead of competing, using the same x402 payments, so an agent that can pay a gateway can pay a Franked deposit.
- Public-sector edition. Participation that stays open to every resident while resisting mass fabrication. Why it matters.
- A franking meter for legitimate senders. Recruiters, press and partnership teams pre-clear their outreach across Franked inboxes.
How Franked fits with Cloudflare and AWS
Cloudflare and AWS have both put HTTP 402 to work. Cloudflare's Monetization Gateway, announced in July 2026, lets customers charge for web pages, datasets, APIs and MCP tools behind Cloudflare. Amazon CloudFront added x402 support through AWS WAF. Both answer one question well: how does a machine pay to consume content?
Franked answers a different one: how does a stranger earn a person's attention?
| Cloudflare Monetization Gateway, Amazon CloudFront x402 | Franked | |
|---|---|---|
| Protects | Content, APIs, datasets and tools | People: inboxes, contact forms, support queues |
| Charges | A toll per request, kept by the site owner | A deposit per first contact, refunded if wanted, otherwise donated |
| Who pays | Automated clients | Anyone new: people by card, agents over x402 |
| Who decides | Price rules set in advance | The recipient, after reading the message |
The two fit together. A business can charge agents for its content through Cloudflare or AWS and put a refundable deposit in front of its inbox and forms with Franked, with agents paying both over the same x402 standard.
Principles that won't change
- Recipients never profit from ignoring people.
- People you know never pay.
- No advertising, and message contents are never sold or used for anything but delivery.
- Payment links only go to authenticated senders, never to forged addresses.
Want to try it or build on it? Write to nariman@franked.email. Yes, it will ask you for a deposit.