Hosted inboxes for bots and automations

Give your bot a real inbox without building a mail stack.

Create an address, receive mail, inspect attachments, and route events to your software without SMTP, IMAP, or OAuth.

  • REST API polling
  • Signed delivery webhooks
  • Attachments and retention built in
Ready in under a minute active
agent-ops@clankermails.com
Domain clankermails.com
Webhook signed + retrying
Latest message Password reset request
6s ago
From alerts@example.com
HTML + text
POST /v1/inboxes/inb_9b4/messages 200 OK

Webhook payload

message.received
{
  "inbox": {
    "address": "agent-ops@clankermails.com"
  },
  "message": {
    "subject": "Password reset request",
    "attachments": []
  }
}
Real inbox addresses
REST API + signed webhooks
Attachments included
Built for bots, not mailbox admins
Why teams buy it

Clanker enough to feel fun. Clear enough to ship with confidence.

ClankerMails should feel like useful infrastructure, not a toy demo. The product carries a bit of bot-builder personality without making the workflow harder.

Real inboxes

Provision inboxes like infrastructure

Choose a local part, pick a domain, and hand your bot a real address without touching SMTP or mailbox hosting.

Delivery options

Poll by API or push by webhook

Keep things simple with REST polling, or wire in signed webhooks the moment new mail lands.

Operational clarity

See the inbox, the payload, and the delivery trail

Recent messages, webhook attempts, and API keys stay in one control surface instead of getting buried in provider dashboards.

How it works

One short setup, then your bot can receive real mail.

The activation path should feel boring in the best way: register, create an inbox, wire your automation, and move on.

01

Create an inbox

Pick an address on a fun domain or a cleaner customer-facing one. The inbox is live immediately.

02

Point your bot at it

Use one API key for polling, or attach a webhook endpoint and verify each delivery with the shared secret.

03

Process real email

Read subjects, bodies, headers, and attachments through one stable interface your automation can actually rely on.

What you do not need

  • SMTP client setup
  • OAuth consent screens
  • Gmail API quota debugging
  • Mailbox hosting for each automation

What you get instead

A clean inbox registry, one API key model, webhook delivery history, and a dashboard your customers or teammates can actually navigate.

Pricing

Start small, pay when the bots become real work.

There is a free path for experiments, and the paid plans are shaped for teams who need more inboxes, more throughput, and longer retention.

Hobby
$0 / month

For single-bot projects and quick experiments.

  • 1 inbox
  • 100 messages per month
  • 5 MB attachments
  • 7-day retention
Start free
Business
$79 / month

For teams handling high-volume mail and longer retention.

  • 50 inboxes
  • 100,000 messages per month
  • 25 MB attachments
  • 90-day retention
  • Priority support
Talk to us
Launch faster

Your bot can have a working inbox before your mail stack ticket even gets triaged.