Field 01 — Declaration of contents · email infrastructure for AI agents
Every inbound message is parsed, classified, extracted to your schema — and screened for prompt injection — before your agent reads a single word.
Free tier. No card. Your agent can sign itself up over MCP.
{
"classification": "invoice",
"confidence": 0.95,
"extraction": {
"vendor": "Globex Corporation",
"amount": 3750
},
"sanitization": [{
"kind": "hidden_text",
"detail": "white-on-white div removed"
}]
}Field 02 — Notice
Raw email is attacker-controlled input. Hidden text, zero-width characters, HTML your parser trusts and your model obeys — piped straight into your agent's context, with its tool access and its credentials. Every inbox API on the market hands you that payload as-is and calls it a feature.
An inbox for an agent isn't a pipe. It's a trust boundary. See how that differs from an inbox API feature by feature, or start with what an AI email agent needs from email.
Field 03 — Mechanism
Fail-closed, always: malware is quarantined, spam is suppressed by default, and injection-risk mail never reaches extraction. Failed attachment scans are never marked clean. Clean mail gets typed JSON; every message keeps its cleaned body, verdicts, and sanitization record for inspection.
Which stage closes which attack, and what each one leaves in the status field: email prompt injection, channel by channel. For the payloads themselves, six real specimens with their sanitization reports.
Field 04 — Proof of processing
{vendor, amount}at 0.95 confidence. The dashboard shows raw-vs-comprehended side by side for every message. This page isn't a mockup of the product.Field 05 — Live inspection
No signup, no API key. Mint a real mailbox below and send it an email — watch it arrive comprehended, right here, in the time it takes the pipeline to run.
We'll mint a real mailbox on the spot. Send it anything — a newsletter, a receipt, a plain note — and watch it come back structured.
Field 06 — Quickstart
Hosted — any MCP client, zero install
https://api.postfleet.ai/api/mcp
Authorization: Bearer $POSTFLEET_KEYLocal — any MCP client, via npx
{ "mcpServers": { "postfleet": {
"command": "npx", "args": ["-y", "@postfleet/mcp"],
"env": { "POSTFLEET_API_KEY": "$POSTFLEET_KEY" }
} } }Claude Code shortcut
claude mcp add --transport http postfleet https://api.postfleet.ai/api/mcp \
--header "Authorization: Bearer $POSTFLEET_KEY"Works with any MCP client — Claude, Cursor, Windsurf, Cline, VS Code. Same six tools, same key, hosted or local — the agent provisions its own address and starts processing mail, no dashboard required. No MCP? Drive it over REST from any framework.
Field 07 — Postage
Taste comprehension. No card.
For a developer shipping agents.
For a team running agents in production.
Sanitization and prompt-injection screening run on every message, on every tier — safety is never metered. You pay for what your agent gets to understand.
Field 08 — Dispatch
agent-hello@mail.postfleet.ai is a Postfleet mailbox — an agent reads it.