Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Setup and use anonymous email accounts on LNemail.net using Bitcoin Lightning payments. Use when agents need email capabilities for 2FA, notifications, or co...
Setup and use anonymous email accounts on LNemail.net using Bitcoin Lightning payments. Use when agents need email capabilities for 2FA, notifications, or co...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Anonymous email accounts via Lightning Network. No KYC, no email required to sign up—just pay with Bitcoin.
LNemail provides fully functional email addresses for 1000 sats/year. Perfect for agents needing: 2FA code reception Anonymous communication Bitcoin/Lightning service notifications API-accessible email without identity requirements
Create a Lightning invoice for email account creation: # Create the account (returns payment hash) curl -X POST https://lnemail.net/api/v1/email # Response: # { # "payment_hash": "abc123...", # "amount": 1000, # "currency": "SATS" # }
# Get the invoice from payment status endpoint curl -X GET https://lnemail.net/api/v1/payment/PAYMENT_HASH # Response when pending: # { # "payment_hash": "abc123...", # "status": "pending", # "lightning_invoice": "lnbc10u1pj..." # } Pay the BOLT11 lightning_invoice using any Bitcoin Lightning Network wallet (e.g., Alby CLI).
After payment confirms (~seconds), check status again: curl -X GET https://lnemail.net/api/v1/payment/PAYMENT_HASH # Response when paid: # { # "payment_hash": "abc123...", # "status": "paid", # "email": "abc123@lnemail.net", # "access_token": "eyJhbG..." # } Save these credentials! Store them securely (e.g., ~/.lnemail/credentials.json).
curl -X GET https://lnemail.net/api/v1/emails \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" # Response: # [ # { # "id": "msg_123", # "from": "sender@example.com", # "subject": "Your 2FA Code", # "received_at": "2024-01-15T10:30:00Z", # "has_attachments": false # } # ]
curl -X GET https://lnemail.net/api/v1/emails/EMAIL_ID \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" # Response: # { # "id": "msg_123", # "from": "sender@example.com", # "to": "abc123@lnemail.net", # "subject": "Your 2FA Code", # "body": "Your verification code is: 123456", # "received_at": "2024-01-15T10:30:00Z" # } Note: HTML content is stripped for security; emails are plain text only.
Sending requires a Lightning payment (~100 sats per email): # Create send request curl -X POST https://lnemail.net/api/v1/email/send \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -d '{ "recipient": "example@example.com", "subject": "Hello", "body": "Message content here" }' # Response: # { # "payment_hash": "def456...", # "amount": 100, # "currency": "SATS" # } Pay the invoice, then check status: curl -X GET https://lnemail.net/api/v1/email/send/status/PAYMENT_HASH # Response when paid: # { # "payment_hash": "def456...", # "status": "paid", # "message_id": "msg_sent_789" # }
EndpointMethodAuthDescription/emailPOSTNoCreate account (returns payment hash)/payment/{hash}GETNoCheck account payment status/emailsGETBearerList inbox messages/emails/{id}GETBearerGet message content/email/sendPOSTBearerCreate send request (returns payment hash)/email/send/status/{hash}GETNoCheck send payment status
Store credentials in ~/.lnemail/credentials.json: { "email": "abc123@lnemail.net", "access_token": "eyJhbG..." } Note: The access_token is the only credential needed for ongoing operations. The payment_hash is only used during initial setup to check payment status — once you have the access_token, it can be discarded.
ServiceCostEmail account (1 year)1000 satsSend email~100 satsReceive emailFree
Plain text only (HTML stripped) Small attachment support 100 sats per outgoing email Account valid for 1 year from payment
2FA reception: Reliable email delivery for verification codes Service notifications: Bitcoin/Lightning service alerts Anonymous signup: Services requiring email without identity link Agent-to-agent comms: Programmatic email between agents
LNemail: https://lnemail.net API Docs: https://lnemail.net (see homepage for full docs) Auth: Bearer token in Authorization header
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.