basemail_skill

This skill lets your AI agent manage its own Basemail.ai inbox, sign in with wallet, register, submit forms, and receive confirmations autonomously.
  • Python

2.6k

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill basemail

  • _meta.json835 B
  • package-lock.json4.0 KB
  • package.json450 B
  • SKILL.md8.0 KB

Overview

This skill gives an AI agent a real email identity on Base chain (yourname@basemail.ai or 0xwallet@basemail.ai). It enables autonomous registrations, form submissions, and receipt of confirmation emails without CAPTCHAs or passwords. Authentication uses wallet signatures so agents can operate without human intervention.

How this skill works

The skill registers an email tied to a Base wallet or a Basename and issues a short-lived auth token after SIWE signature verification. Agents can send email via the API and poll the inbox endpoints to list or read messages. Wallets may be provided via environment variable, a file path, or generated and managed locally (encrypted by default).

When to use it

  • Automate service sign-ups, newsletter subscriptions, and event registrations for an agent.
  • Submit forms or receive confirmation emails without human involvement.
  • Test flows that require email delivery for autonomous agents.
  • Give an agent a verifiable, decentralized email identity using Basename or a wallet address.

Best practices

  • Prefer the environment variable method for private keys to avoid writing secrets to disk.
  • Use managed wallets with encryption enabled; back up the mnemonic manually and never commit it to version control.
  • Set file permissions to owner-only (chmod 600) for any private-key files or tokens.
  • Avoid storing unencrypted keys on shared machines; use --no-encrypt only in fully trusted environments.
  • Rotate or revoke keys and tokens when an agent is decommissioned.

Example use cases

  • An agent signs up for a service and confirms the account receipt without human help.
  • A bot submits forms and captures confirmation emails for logging and auditing.
  • QA automation that verifies email-based flows (registration, reset, receipts) using a dedicated agent mailbox.
  • A decentralized identity workflow where a Basename maps to a friendly email address for agents.

FAQ

Yes—register a Basename on Base and run registration with --basename to upgrade from 0x...@basemail.ai to yourname@basemail.ai.

Do I need to store a password?

No. Authentication is via wallet signature (SIWE). Managed mode may encrypt the private key with a password locally, but no service password is required.

What methods exist to provide a wallet?

You can supply a private key via an environment variable (recommended), point to an existing key file, or let the skill generate and manage a wallet (encrypted by default).

Is CAPTCHA required?

No. Wallet signature serves as proof of identity so CAPTCHAs are not needed.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational