AgentMail raised $6M Tuesday. General Catalyst led. Paul Graham wrote the check personally.
The pitch: every AI agent gets an email address. Not a forwarding alias, not a webhook endpoint -- a real, addressable email identity that the agent controls and responds through autonomously.
That's one half of what an agent needs to exist in the world. The other half is money.
An agent with an email and no wallet can communicate. An agent with both can work.
The Identity Stack Problem
Most agent frameworks right now treat identity as an afterthought. You deploy an agent, it calls tools, it executes tasks, and somewhere in the logs there's a UUID that technically represents it. That's not identity -- that's a process ID.
Real identity means:
- a persistent, addressable endpoint others can reach you at
- an economic handle that can receive and send value
- control over both that doesn't route through a third party
AgentMail solves the first. agent-wallet-sdk solves the second. Used together, you get something close to a full autonomous agent identity.
AgentMail: What You Get
An email address your agent actually controls. The agent can receive emails, parse them, respond to them, and route actions based on their content -- without a human in the loop.
The use cases are not abstract. An enterprise agent that negotiates API access agreements over email. A personal agent that handles contract routing. A trading agent that receives settlement confirmations. An AI concierge that manages calendar requests through the same channel every human uses.
$6M from people who've seen a lot of agent startups says the demand is real.
agent-wallet-sdk: What You Get
Non-custodial wallet infrastructure for AI agents. The agent holds the keys. Seventeen chains. No KYC. No managed custody. No third party between your agent and its funds.
The SDK handles:
- Wallet creation and key management
- Multi-chain transaction routing (Ethereum, Base, Solana, 14 others)
- Spend limits configurable at the wallet level
- ERC-6551 Token Bound Accounts for permission revocation via NFT rotation
- Chain-neutral API so your agent code doesn't care which chain it's running on
Wiring Them Together
The integration pattern is straightforward. Your agent gets:
- An AgentMail address -- let's say procurement@agents.yourcompany.com
- A non-custodial wallet address from agent-wallet-sdk
Now when a vendor emails the agent to negotiate a data subscription, the agent can:
- Parse the terms via AgentMail
- Evaluate the offer against configured spend limits
- Approve the transaction via agent-wallet-sdk
- Send a signed confirmation back via email
No human touched that workflow. No managed custody provider touched the funds. The agent acted.
That's what full agent identity enables.
Why the Stack Matters Now
The agent economy is moving toward autonomous economic actors. Not assistants that route to humans for approval -- actual agents that transact.
AgentMail gives agents a communication identity. agent-wallet-sdk gives them an economic identity. The combination is the minimum viable identity stack for an agent that can participate in the economy without constant human supervision.
Neither piece works as well alone. An agent with only email is a sophisticated autoresponder. An agent with only a wallet is a script that can spend money but can't negotiate the deal. Both together -- that's an autonomous economic actor.
GitHub: github.com/AI-Agent-Economy/agent-wallet-sdk
AgentMail: agentmail.to
This article was written with AI assistance. All technical claims, code, and architectural decisions were validated by the author.
Top comments (0)