Give your LangChain agent a real inbox. June 13, 2026 AgentMail ships an official LangChain integration. One pip install gives any LangGraph agent its own inbox to send from, reply in, search, and react to. Engineering integrations developer-resources AgentMail's official LangChain integration is live. One pip install gives any LangGraph agent its own inbox it can send from, reply in, search, and react to. The problem. Your agent can reason and call tools, but it can't receive anything. That's fine until it hits the real world. The agent tries to sign up for a service and the confirmation email goes nowhere. It needs an OTP and there's no inbox to read it from. Someone replies to a message it sent and the reply vanishes. Most "email for agents" is send-only (SendGrid, Mailgun, raw SMTP), which covers the easy half. The half that matters is receiving: catching the verification code, reading the reply, reacting to what lands. You can build that yourself. Stand up an IMAP client, parse MIME, dedupe threads, verify webhook signatures, keep an address alive across runs. That's a few hundred lines of plumbing before your agent sends its first email. Why langchain. You already build the agent here. LangChain is the default framework for wiring up tools, memory, and control flow, and LangGraph is where you run the multi-step logic. You're not looking for a new place to write agent code. You have one. What you want is for the inbox to show up as tools inside the graph you already have. Why AgentMail. AgentMail is an inbox as an API. One call gives an agent its own address that can send and receive. The address persists across runs, so an agent that gets logged out signs back in instead of starting over. A webhook fires the moment a message arrives, so you react to inbound mail instead of polling for it. The receive side is the point. It's what lets an agent get through a signup wall, read its own OTP, and pick a thread back up next week. Why the union matters. langchain-agentmail wraps the AgentMail SDK as standard LangChain tools, plus a document loader and a retriever. The plumbing from the first section (IMAP, MIME parsing, threading, webhook verification) is gone. You install the package and the inbox becomes a toolkit your LangGraph agent already knows how to call. pip install langchain-agentmail export AGENTMAIL_API_KEY="your-api-key" What you can do with it. Give agents their own inboxes. Provision a dedicated address per agent so it can send and receive on its own. The toolkit hands the model one tool per operation: create an inbox, list and read threads, send, reply, label, draft. Triage and reply. Read recent threads, summarize what's new, and reply inside the same thread with the right In-Reply-To headers. Hand the whole toolkit to a ReAct agent and that's a few lines: from langchain.chat_models import init_chat_model from langgraph.prebuilt import create_react_agent from langchain_agentmail import AgentMailToolkit model = init_chat_model(model="claude-sonnet-4-6", model_provider="anthropic") agent = create_react_agent(model, AgentMailToolkit.from_api_key.get_tools response = agent.invoke({ "messages": [("user", "Check my inbox for anything new. Summarize the most recent thread in 2 sentences.",)]}) Stage and schedule sends. Use the draft tools to compose iteratively, revise, and ship, or set a delivery time with send_at: from langchain_agentmail import AgentMailCreateDraftTool AgentMailCreateDraftTool.invoke({ "inbox_id": "ib_...", "to": "[email protected]", "subject": "Following up", "text": "Circling back on this.", "send_at": "2026-06-20T09:00:00Z", # omit to send on demand}) RAG over email. Load messages as LangChain Documents and index them into a vector store for semantic search across the inbox. A bundled retriever does keyword search with no embeddings: from langchain_agentmail import AgentMailLoader, AgentMailRetriever docs = AgentMailLoader(inbox_id="ib_...", labels=["inbox"], limit=50).load retriever = AgentMailRetriever(inbox_id="ib_...", k=5) hits = retriever.invoke("invoice") And to react to inbound mail instead of polling, the webhooks extra ships a FastAPI router with signature verification built in: from fastapi import FastAPI from langchain_agentmail.webhooks import AgentMailEvent, create_fastapi_router async def on_event(event: AgentMailEvent) -> None: if event.event_type == "message.received": # drive your LangGraph agent here... app = FastAPI app.include_router(create_fastapi_router(on_event), prefix="/agentmail") Try it. pip install langchain-agentmail The reference is on the LangChain docs, the package is on PyPI, and the source is on GitHub. Give the agent you already built an inbox and see what it does with it. AgentMail gives your agents real inboxes. Create inboxes via API. Send and receive Emails with 0 complexity. Free to start.

How to give your Browser Use agent an email inbox using AgentMail. April 3, 2026 Browser Use and AgentMail are partnering so every cloud session gets its own inbox - signups, OTPs, and verification links without a human. Engineering browser use browser use cloud browser automation Most of the web is locked behind an email address. Sign up for a service and you need an email. Confirm your account and you have to check your inbox. Whether you're resetting a password, completing 2FA, or getting a receipt, it all comes back to email. Most services need an email address to create an account, whether it's for verification links, OTP codes, or magic links. If a browser agent doesn't have its own inbox, it usually can't get past these steps. Browser Use is a top tool for letting AI agents control a browser, with 85,700 GitHub stars since November 2024. Still, even the best browser agent gets stuck when a site asks you to check your email to continue. That changes today. AgentMail gives AI agents their own email inboxes. With Browser Use, agents can also control a browser. When you combine these features, your agent can manage the entire web, even tasks that once needed a person to check their inbox. Email is now built into every Browser Use session. AgentMail, Inc. is partnering with Browser Use to bring email inboxes to every agent session. There's no API key, no configuration, and nothing you need to set up. If you use Browser Use Cloud, AgentMail is already there. Each session gets its own inbox automatically. All you have to do is give the agent a task. Ask it to sign up for Instagram. It will create a new inbox right away, fill in the email address, submit the form, wait for the verification email, confirm the account, and move on. The example above shows a real Browser Use Cloud session. The agent creates an inbox using AgentMail, picks up the address automatically, and fills in the form fields name, username, birthday, password - and is mid-signup without any human involvement. No copy-pasting credentials. No tab-switching to check an inbox. The agent handles the whole thing. Each session has its own separate inbox. When the session ends, the inbox disappears. Every run starts fresh. What you can do now. Before now, browser agents would get stuck whenever an email was needed. That's no longer the case. Here are a few things you can do now: Account creation: Sign up for any service that needs email verification. The agent manages the inbox, the verification link, and everything that comes after. 2FA and OTP flows: Authentication codes sent during a session go straight to the agent's inbox and are picked up automatically. No pauses, no interruptions. Confirmation and receipt emails: The agent can use the emails it receives, not just send them. Booking confirmations, order receipts, and access links can all be processed in real time. Research and competitive monitoring: The agent can handle trial signups, newsletter subscriptions, and product registrations. It signs up, gets access, and reports back. This is what happens when a browser agent can handle the entire process, not just the steps that don't require a login. For developers: use it in your own code. If you're building with Browser Use open source and want this feature in your own setup, you can connect it directly with AgentMail. For this option, you'll need an AgentMail API key. Sign up here. You can find the integration in Browser Use's official examples under examples/integrations/agentmail/. It adds two tools to the agent: one for getting the inbox address and one for fetching the latest email. import asyncio import os os.environ["BROWSER_USE_API_KEY"] = "your-browser-use-key" os.environ["AGENTMAIL_API_KEY"] = "your-agentmail-key" from browser_use import Agent, ChatBrowserUse, Browser from agentmail import AsyncAgentMail from email_tools import EmailTools # Provided in the Browser Use example (see examples/integrations/agentmail/) async def main: client = AsyncAgentMail(api_key=os.environ["AGENTMAIL_API_KEY"]) inbox = await client.inboxes.create print(f"Created inbox: {inbox.inbox_id}") email_tools = EmailTools(client, inbox=inbox) browser = Browser(use_cloud=True) agent = Agent( task=f"Sign up for Reddit using {inbox.inbox_id} and verify the account.", llm=ChatBrowserUse(model="bu-2-0"), browser=browser, tools=email_tools,) result = await agent.run print(f"Result: {result}") if __name__ == "__main__": asyncio.run(main Get started. If you use Browser Use Cloud, there's nothing to set up. Just open cloud.browser-use.com and start building. If you're working on something interesting with this, AgentMail, Inc.'d love to hear from you. AgentMail gives your agents real inboxes. Create inboxes via API. Send and receive Emails with 0 complexity. Free to start.

AgentMail secures $6M to develop an email platform for AI agents. A few years back, AI agents primarily consisted of basic chatbots with limited capabilities. While interest was present, issues regarding reliability, security, and costs kept the technology within a niche market of early enthusiasts. Fast forward to today, the landscape has transformed dramatically. Initially, coding agents like Claude Code, Codex, and Cursor gained traction among developers, enabling them to tackle tasks such as large-scale debugging and executing marketing campaigns. Nowadays, AI agents are utilized for a wide range of activities, including calendar management and meeting scheduling. The launch of OpenClaw earlier this year accelerated this trend, allowing users to operate their personalized AI agents continuously. According to trends in the tech industry, AI agents are anticipated to proliferate online, acting on behalf of users for various tasks like shopping and communication, thus automating numerous responsibilities. A startup based in San Francisco, AgentMail, is keenly aware of this potential future and has developed an email service tailored specifically for AI agents. Their platform offers an API that enables AI agents to possess their own email accounts, supporting two-way conversations, message parsing, threading, labeling, searching, and response functionality. Recently, AgentMail disclosed that it secured $6 million in seed funding, led by General Catalyst, with contributions from Y Combinator, Phosphor Capital, and several angel investors including Paul Graham and Dharmesh Shah. In conjunction with this funding, AgentMail introduced an onboarding API, facilitating AI agents to independently register and create their email accounts. The platform also allows for manual management of inboxes, permissions, allowlists, and API keys. Co-founder and CEO Haakam Aujla stated that AgentMail was designed to replicate the inbox experience familiar to users of services like Gmail or Outlook, but without the user interface elements necessary for human operation. (It is worth noting that the platform also includes a user-friendly interface for managing various agent inboxes and handling email communications.) "When you look at Gmail, you find numerous threads, each containing multiple messages that can include attachments. It's crucial to label, search, filter, reply, and forward these messages," Aujla explained. "We aimed to enable our agents to perform similar functions without needing to interact with a user interface since that would be inefficient for them. They should simply execute API calls." Since its inception as part of Y Combinator's Summer 2025 cohort, AgentMail has gained tens of thousands of human users and hundreds of thousands of "agent users," in addition to more than 500 B2B clients. Initially, the growth was slow as AI agents were not yet mainstream. AgentMail primarily targeted B2B clients looking to enhance their email communications. However, after OpenClaw emerged onto the market in late January, AgentMail experienced a surge in user registrations, tripling in one week and quadrupling in the following month as demand for email functionality for agents increased. This surge came at a crucial time, as traditional email services like Gmail impose restrictions on usage rates and volumes through their APIs. In contrast, AgentMail offers a generous free tier, along with various paid plans and enterprise options. Nevertheless, there are inherent risks associated with granting email capabilities to AI agents. To mitigate potential misuse, Aujla revealed that AgentMail employs multiple safeguards: agent inboxes can only send a maximum of 10 emails per day unless verified by a human; the system imposes limits on activity levels; monitors bounce rates; and conducts random checks on new accounts for sensitive terms. Beyond providing a means for bots to handle emails, Aujla emphasizes that AgentMail's broader mission is to establish an identity framework for AI agents: "Our aim is to empower agents to utilize email like humans do. However, the fundamental purpose of email is not just communication; it serves as an identity tool. Numerous startups work on developing new identity protocols for agents, but our approach is to leverage existing, successful human frameworks that are already deeply embedded in the online ecosystem." In conclusion, Aujla states, "By assigning an email address to an agent, it can now interact with virtually any software service available."