Lumbox gives any AI agent its own inbox and phone number. It reads what arrives, replies, signs in with the codes it gets, and calls your tools. Bring the agent you already run, or build one here.
Free for 3 inboxes. No credit card.
Works with the agent you already run
What your agent gets
Login codes are one tool out of six. The same key covers all of them.
A real address on trylumbox.com or your own domain. Every message arrives parsed to JSON, threaded with the ones before it.
From your domain with DKIM, SPF and DMARC set up for you, or bulk-send 100 messages a request.
Texts land in the same inbox and come back through the same API as email.
Codes, magic links and verification links come back as JSON. Passwords and 2FA secrets sit in an encrypted vault.
Webhooks fire on new mail, replies, clicks, drafts and escalations, or the agent blocks on /wait until mail lands.
104 MCP tools for Claude Code and Cursor, SDKs for Node and Python, and plain REST for everything else.
Two ways in
Claude Code, Cursor, the OpenAI Agents SDK, LangChain or your own loop. Your agent keeps its brain, and Lumbox gives it an address, a mailbox and the calls to use them.
const inbox = await lumbox.createInbox({ name: "ava" }); // blocks until mail arrives const email = await inbox.waitForEmail({ timeout: 120 }); const answer = await myAgent.run(email.text_body); await inbox.reply({ email_id: email.id, text: answer });
Give an inbox instructions and your knowledge. It answers what arrives, calls your own HTTP tools, and hands anything uncertain to you as a draft or an escalation.
Channels
People reach your agent however they like, and your agent reads it the same way every time.
Every message is parsed on arrival: text, threads, codes, links and a category, as JSON. Send and reply from the same address, on your domain or ours.
A number for your agent that sends and receives texts through the same inbox and the same API. We are opening it in batches.
Live today: forward texts from your own phone into an inbox, and /otp returns the code. Setup guide →
Use cases
Your assistant gets its own address, signs up and logs in for you, joins your calls and saves the transcript, and asks before sending anything it is unsure of.
Build yours →An agent answers support@ from your docs and your order data. Anything it cannot answer goes to a person with the full thread.
Set up support →Log in to portals for your customers with one inbox each, so codes and history never cross between customers.
See the guide →Send from your own domain and let the agent read the replies and answer in the same thread.
Email API →Email API
Send, reply, forward and bulk-send up to 100 messages a request from your own domain. Replies come back to the inbox that sent them, so you can hand the conversation to an agent whenever you want.
Explore the email API →await inbox.send({ to: "maria@acme.com", subject: "Your invoice for October", html: "<p>Hi Maria, it is ready.</p>", });
Pricing
Free
$0/mo
No card needed
Starter
$9/mo
Custom domains
Pro
$29/mo
For production fleets
Scale
$99/mo
High volume
Yes. Lumbox gives each agent its own inbox with one API call. The agent reads what arrives, replies, signs in with the codes it receives and calls your tools. Every message is parsed to JSON with codes, links and a category.
Yes. Turn on the agent for an inbox, write its instructions, add your help docs as a knowledge base and connect your own HTTP tools. It drafts each reply for you to approve, or sends on its own if you choose. Paid plans include a monthly AI credit, so you do not need a model key.
Today you can forward texts from your own phone into a Lumbox inbox, and the same /otp call returns the code. Dedicated phone numbers for agents are in early access, and you can join from the homepage.
Give the site the agent's Lumbox address, then call GET /v1/inboxes/:id/otp. It waits until the code arrives and returns it as JSON. Verification and magic links are extracted the same way.
Yes. There is a hosted MCP server with 104 tools, a REST API, and SDKs for Node and Python. Any agent that can make an HTTP call can use it.
We use cookies to understand how people use Lumbox. See our privacy policy.