Mailgent vs building it yourself
You could stitch together SES, a secrets manager, a TOTP library, a calendar API, a DID toolkit, and a wallet. Here's what that actually costs versus one API call.
Everything Mailgent does, you could build. Email through SES, secrets in a vault service, TOTP with a library, a calendar API, a DID toolkit for did:web, and a wallet with on-chain payments. The pieces all exist.
The question is whether assembling and operating that stack is the best use of your time when one signup call gives you all of it, already integrated and scope-gated under a single identity.
The hidden cost of DIY
Each piece is a project. Email means domains, DKIM, SPF, reputation, and inbound parsing. Secrets means encryption, rotation, and access control. 2FA means secure secret storage and code generation. DIDs mean key management and document hosting. Payments means wallets, mandates, and on-chain settlement.
Then you have to make them speak to one identity, keep them secure, and maintain them. The integration glue is where the time goes, and it never stops needing attention.
What one call replaces
Mailgent's agent-signup returns a platform key and an identity with an address, scopes, and the keys behind it — email, vault, 2FA, calendar, signing, and wallet all wired together and gated by that identity's scopes.
You get to the actual agent logic on day one instead of month three.
curl -X POST https://api.mailgent.dev/v0/agent-signup -d '{}'
# -> platform_key, address @mailgent.dev, signing key, scopes
# email + vault + 2FA + calendar + identity + wallet, ready to useWhen DIY makes sense
If you have hard requirements that demand bespoke infrastructure — specific compliance boundaries, an existing identity system you must extend, or self-hosting mandates — building may be warranted. For most teams shipping agents, the integrated stack wins on time and security.
FAQ
Is Mailgent a lock-in?
Capabilities are standard underneath — did:web identity, real email, USDC on Base — so you're building on open primitives, not a proprietary cage.
Can I adopt just the inbox first?
Yes. Use mail alone and grant more scopes as you need the vault, 2FA, calendar, or wallet.
How fast can I start?
One signup call provisions an agent with everything wired together. You can be sending mail in minutes.
Give your agent an inbox.
A real email address, a vault, 2FA, and an identity in one API call.