neynar-inbox

What This Skill Does

The neynar-inbox skill provides a dedicated, headless email infrastructure designed specifically for AI agents. Unlike traditional email providers that require complex OAuth flows, browser interactions, or manual verification, this service operates entirely via a clean REST API. It allows your agents to programmatically generate unique email addresses, send outgoing correspondence, and monitor incoming messages. This skill bridges the gap between the internet's most ubiquitous communication protocol and the autonomous nature of AI agents, enabling them to register for services, communicate with users, or handle inbound customer support inquiries without human intervention.

Installation

To add this capability to your agent, execute the following command in your terminal within the OpenClaw environment:

clawhub install openclaw/skills/skills/rishavmukherji/neynar-inbox

Once installed, you must first create a mailbox using the registration endpoint. This will return a critical API key. You must save this key securely within your environment variables or agent secret store, as it cannot be recovered if lost. Authentication for all subsequent requests is handled via the Bearer token scheme using this API key.

Use Cases

• Agent Autonomy: Allow agents to sign up for beta programs or waitlists that require email verification.
• Support Automation: Create an automated triage system where an agent monitors an inbox and responds to customer inquiries based on specific keywords.
• Transaction Alerts: Configure your agent to receive automated notification emails from financial or web services and take action based on the content.
• Collaborative Workflows: Agents can send status reports or data summaries to human stakeholders via email directly from the task execution flow.

Example Prompts

1. "Check my inbox for any new messages regarding the 'Project X' update and summarize the core requirements found in the body."
2. "Send an email to [email protected] asking for an extension on the current API quota limit, referencing my account ID 550e8400."
3. "Rotate my current mailbox API key for security purposes and update the stored environment variable to the new value."

Tips & Limitations

• Security: The provided API key is the only form of access. If compromised, anyone can access your emails. Rotate your keys regularly using the /rotate endpoint.
• Polling: Since this service does not use traditional push notifications, if you require immediate responses, implement a recurring cron job to poll for new emails every 30 to 60 seconds.
• Storage: Use the DELETE method for emails that are no longer needed to maintain a clean environment and avoid hitting any underlying storage limits.
• Format: The API provides both plain text and HTML bodies. Ensure your agent is configured to parse HTML if you expect rich-text notifications.