← Back to Skills Marketplace
kumard3

Lumbox

by Kumar Deepanshu · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
27
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install lumbox
Description
Email infrastructure for AI agents with zero-human setup. Self-provision an inbox in one command (no account creation, no console, no human), send and receiv...
README (SKILL.md)

Lumbox

Lumbox gives agents real email inboxes. The difference from other email providers: an agent provisions itself. No human creates an account, no console visit, no dashboard.

Setup (agent does this itself)

If LUMBOX_API_KEY is not set:

npx lumbox signup --source openclaw

This creates an org + API key and saves it to ~/.lumbox/config.json. Tell your human where the key lives. All later commands read it automatically; LUMBOX_API_KEY env overrides the file.

Free tier: 3 inboxes, 500 inbound + 100 outbound emails/month. Signup is limited to 3 orgs/hour per IP. Paid plans from $9/month at https://lumbox.co/pricing.

Get an email address

npx lumbox inbox create --name assistant

Returns JSON: {"id": "inb_...", "address": "[email protected]"}. Use that address anywhere a signup form wants an email.

Wait for an OTP / verification code

npx lumbox wait-otp --inbox inb_... --timeout 120

Blocks until a verification email arrives, parses the code out, prints {"code": "847291", "from": "...", "subject": "...", ...}. No polling loops, no regex on your side. Magic links and verification URLs are also extracted (GET /v1/inboxes/:id/wait returns the full parsed email).

Send and reply

npx lumbox send --inbox inb_... --to [email protected] --subject "Update" --text "Done."
npx lumbox inbox list

Replies thread correctly via POST /v1/inboxes/:id/reply (REST) with the original message id.

REST API (no CLI needed)

Base URL https://api.lumbox.co, auth Authorization: Bearer $LUMBOX_API_KEY:

POST /v1/orgs                       self-signup, returns api_key (unauthenticated)
POST /v1/inboxes                    create inbox
GET  /v1/inboxes/:id/wait           long-poll next email (parsed: otp, links, category)
GET  /v1/inboxes/:id/otp            long-poll just the OTP code
POST /v1/inboxes/:id/send           send
POST /v1/inboxes/:id/reply          reply in-thread

See references/API.md for request/response shapes.

Full toolset via MCP (87 tools)

openclaw mcp add lumbox -- npx @lumbox/mcp-server

or HTTP at https://mcp.lumbox.co with the same Bearer key. Adds browser automation sessions, an encrypted credential vault, TOTP 2FA codes, webhooks, custom domains, and contact lists — so one key covers the whole "sign up for a service" flow: inbox → form fill → OTP → store creds.

Docs: https://docs.lumbox.co • Agent signup guide: https://docs.lumbox.co/agent-signup

Usage Guidance
Review before installing. Use this only for accounts and correspondence you explicitly authorize, prefer scoped inbox keys where possible, keep the local API key protected, and avoid using it for sensitive personal or production accounts unless you trust Lumbox with email contents, OTPs, magic links, and stored credentials.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The stated purpose is coherent: agent-owned inboxes, OTP retrieval, sending/replying, and account-signup support. The concern is breadth: the same skill advertises external account signup, verification-code handling, browser automation, credential storage, and TOTP generation, which can materially affect third-party accounts.
Instruction Scope
The use guidance is broad, including any time an agent needs an email address for service signups, verification codes, or correspondence. It does not require explicit user approval before account creation, OTP retrieval, sending mail, browser automation, or credential storage.
Install Mechanism
The artifact contains markdown instructions only, but setup relies on live npx packages and an MCP server rather than pinned local code. That is disclosed, but users must trust the external package and hosted service at runtime.
Credentials
Use necessarily routes inbox contents, OTPs, magic links, outbound messages, and related metadata through Lumbox infrastructure. The skill identifies the API and MCP endpoints, but gives little privacy, retention, or secret-handling guidance for sensitive email and authentication data.
Persistence & Privilege
The setup flow creates an org/API key and saves it to ~/.lumbox/config.json for automatic future use. The same bearer key is described as covering inboxes plus browser automation, credential vault, TOTP, webhooks, domains, and contacts, with no clear cleanup, revocation, or least-privilege defaults.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install lumbox
  3. After installation, invoke the skill by name or use /lumbox
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: self-signup via npx lumbox signup, inbox create, wait-otp with parsed codes, send/reply, MCP server pointer
Metadata
Slug lumbox
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Lumbox?

Email infrastructure for AI agents with zero-human setup. Self-provision an inbox in one command (no account creation, no console, no human), send and receiv... It is an AI Agent Skill for Claude Code / OpenClaw, with 27 downloads so far.

How do I install Lumbox?

Run "/install lumbox" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Lumbox free?

Yes, Lumbox is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Lumbox support?

Lumbox is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Lumbox?

It is built and maintained by Kumar Deepanshu (@kumard3); the current version is v1.0.0.

💬 Comments