kumard3
- 8 skills
- 0 followers
- 13 hours ago last updated
- ▌ Lumbox · kumard3Give an AI agent its own email - create inboxes, send and receive email, wait for OTP codes, all self-service with no human signup. Use when an agent needs an email address to sign up for services, receive verification codes, or manage correspondence.
- ▌ Lumbox MCP · kumard3Connect an AI agent to the Lumbox MCP server for email - create inboxes, extract OTPs, wait for verification codes, send/reply/forward, and search email as native MCP tools. Use when wiring Lumbox into Claude Code, Cursor, or any MCP-compatible client.
- ▌ Lumbox Sdk · kumard3Use the Lumbox SDK to give AI agents email - create inboxes, long-poll for OTPs, and send/reply/forward from TypeScript or Python. Use when integrating Lumbox into agent code with the official npm or PyPI package instead of raw HTTP.
- ▌ Send Email · kumard3Send an email from a Lumbox inbox to any recipient. Handles threading, attachments, and returns a message ID for future replies.
- ▌ Wait For Otp · kumard3Block until an OTP code arrives at a Lumbox inbox and return the parsed code. Avoids polling loops - the request long-polls the server.
- ▌ Create Lumbox Inbox · kumard3Create a fresh Lumbox email inbox for an AI agent. Returns a real email address the agent can receive OTPs, magic links, and messages at.
- ▌ Email For AI Agents · kumard3Patterns and guidance for giving AI agents their own email - when an agent needs an inbox, how to handle OTP/2FA and verification links, and how agent-native email differs from transactional and OAuth-inbox APIs. Use when designing an agent that must sign up for services, verify identity, or correspond by email.
- ▌ Agent Email Patterns · kumard3 bundleProduction patterns for AI agents that use email - signup-and-verify, email-based 2FA during browser automation, multi-agent inbox isolation, agent-to-human threads, and security hardening against prompt injection. Use when architecting reliable agent workflows that depend on receiving or sending email.