Inbox API
Create, pause, search, and route agent inboxes from code.
[ 000 ] EMAIL FOR AGENTS
Give everyagent aninbox.
hedwig.bot gives AI agents real email inboxes. Create addresses, receive messages, read attachments, reply in the same thread, and send every update to your app.
// NO SHARED HUMAN INBOXES// BUILT FOR AI AGENTS
[ What we offer ]Not AI inside your inbox.
Not AI inside your inbox.
Real inboxes for your AI.
Agents should not share a teammate's Gmail account, scrape notification emails, or wait for a person to forward a code. hedwig.bot gives them their own addresses, messages, threads, files, identity, and updates.
Threads and replies
Keep context together so agents can reply like part of the conversation.
Webhooks
Send every new message and delivery update to your app.
SDKs and CLI
Use TypeScript, Python, cURL, or terminal workflows.
Secure attachments
Scan, store, and share files with controlled links.
Domain controls
Use real sender identity with authentication and health checks.
[ What it does ]
One API for agent email.
SELECT MODULE01 / 06
MODULE_01
Ready-to-use inboxes
CREATE
Create a real email address for an AI agent in one API call. Use it for signups, customer conversations, documents, and follow-ups without sharing a human inbox.
CREATE164 ms
DOMAINverified
STATEready
[ By the numbers ]
Built for agents that do not sleep.
An agent inbox should be easy to create, easy to monitor, and easy to connect to the systems your product already uses.
[ Use cases ]
Where agents need email to finish the job.
Browser agents
Give a browser agent a real inbox so it can receive codes, confirm accounts, and keep going without a person forwarding messages.
Executive assistants
Let an agent coordinate meetings, reply in the same thread, summarize commitments, and escalate only messages that need judgment.
Document processors
Receive invoices, receipts, statements, and contracts, then pass clean files and email context into your parser.
Support routers
Turn shared inbox chaos into structured events that agents can triage, enrich, route, and resolve.
[ Agent workflow ]
Incoming email becomes agent context.
01
Receive
A real address accepts the message and tells your app it arrived.
02
Understand
The sender, body, thread, and attachments become clean context.
03
Act
Your agent replies, routes, extracts, schedules, or escalates.
[ FAQ ]
Frequently asked questions.
Why do AI agents need their own email inboxes?
Email is still how many businesses verify identity, send documents, and run workflows. Agents need their own inboxes to receive codes, join conversations, handle attachments, and act in systems that already use email.
How is this different from a sending API?
Most email APIs focus on sending notifications. hedwig.bot is built for two-way agent work: inboxes, incoming email, thread history, attachments, search, and replies in one API.
Can I use my own domain?
Yes. The product model supports custom domains, mailbox routing, sender authentication, and deliverability visibility so agent mail does not look like a disposable workaround.
What happens when an agent receives an attachment?
Your app receives file details and a controlled file link, so the agent can classify, extract, summarize, or pass the attachment to another tool.
Is this only for autonomous agents?
No. It also works for agent-assisted teams, browser automation, support systems, back-office document flows, and any product that needs many real inboxes managed by software.
[ Start ]