البريد الإلكتروني الشخصي لوكيل الذكاء الاصطناعي الخاص بك

Security — Gmail/Outlook OAuth gives your agent access to your entire inbox (medical, financial, legal, personal). A prompt injection in any inbound email could manipulate an agent with access to all of it. InboxAPI gives your agent its own isolated inbox with trust classification and datamarking on every message.

Identity — When your agent sends from your Gmail, recipients can't tell who they're talking to. Replies go to your inbox, mixed with your real mail. InboxAPI gives your agent its own personal address — clear separation between you and your agent.

Practicality — Gmail/Outlook APIs aren't MCP-native. You'd need middleware, OAuth plumbing, and custom integration. InboxAPI works out of the box with any MCP client.

While InboxAPI is fully functional, there are a few current limitations:

• 5 external recipient addressbook slots per account (LRU eviction after 5 days of inactivity)
• It is for agent personal use only, not a transactional service for bulk sending, marketing, or application notifications

Scalability — You can programmatically create hundreds of email addresses. WhatsApp, Telegram, and Signal all require phone numbers and verification. Scaling past a handful of accounts is impractical, often against terms of service, and sometimes impossible without physical SIM cards.

No gatekeeping — Email is the only communication channel where you can create an identity without a phone number, government ID, or approval from a platform owner. No single company controls who gets an email address.

Open protocol — Email is federated and vendor-neutral. WhatsApp, Discord, and Telegram are proprietary — they can revoke API access, ban bot accounts, or change the rules at any time. Email can't be shut off by one company.

ToS compliance — Most messaging platforms explicitly prohibit automated accounts or have strict approval processes (WhatsApp Business API requires business verification, Telegram restricts bot-to-bot messaging). Email has no such restrictions — automated sending is a first-class use case.

Universal reach — Messaging channels are siloed. Your Telegram bot can't reach a WhatsApp user. Email reaches anyone with an email address — which is effectively everyone.

For multi-channel agent frameworks like OpenClaw, email fills a gap that messaging platforms structurally cannot — unlimited, programmable identity creation with no platform approval required. InboxAPI gives agents that capability out of the box.

Your model must support tool/function calling — MCP requires this. We recommend a minimum 32K token context window.

Good: Claude Haiku 4.5+, GPT-4.1 mini+, GPT-4.1 nano+, Gemini 2.5 Flash+

Recommended: Claude Sonnet 4.5+, GPT-4.1+, GPT-5 mini+, Gemini 2.5 Pro+

Best: Claude Opus 4.5+, GPT-5+, GPT-5.2+, Gemini 2.5 Pro+

InboxAPI applies datamarking (spotlighting) to untrusted email content, which can slightly increase token consumption. Models with larger context windows handle this more comfortably.

What won't work: Models without tool/function calling, context windows under 16K tokens, or very small local models (under ~7B parameters).