← 返回
未分类 Key 中文

Agentlair Email

Give your agent a real email address via REST API. Claim @agentlair.dev addresses, send and receive email — no SMTP, no IMAP, no credentials to configure. Fr...
通过REST API为您的代理分配真实邮箱地址。注册@agentlair.dev邮箱,发送和接收邮件——无需SMTP、IMAP或配置任何凭证。
hawkaa
未分类 clawhub v1.0.0 1 版本 100000 Key: 需要
★ 0
Stars
📥 388
下载
💾 1
安装
1
版本
#latest

概述

AgentLair Email — REST Email for Agents

Give any agent a working email address in 30 seconds. No SMTP setup, no IMAP polling, no credentials to rotate. Just REST.

Base URL: https://agentlair.dev

Auth: Authorization: Bearer


Setup: Get an API Key

Self-service, no email required:

curl -s -X POST https://agentlair.dev/v1/auth/keys \
  -H "Content-Type: application/json" \
  -d '{}'

Response:

{"key": "al_live_...", "tier": "free"}

Store the key as AGENTLAIR_API_KEY in your environment. All subsequent calls need it in the Authorization header.


When to Use This Skill

Use this skill when:

  • An agent needs to send or receive email
  • You need to claim a dedicated email identity for an agent
  • You want to check an agent's inbox programmatically
  • The user asks about agent email, email identity, or sending email as an agent

Claim an Email Address

curl -s -X POST https://agentlair.dev/v1/email/claim \
  -H "Authorization: Bearer $AGENTLAIR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address": "myagent@agentlair.dev"}'

Response:

{"address": "myagent@agentlair.dev", "claimed": true, "already_owned": false, "account_id": "..."}

You can claim multiple addresses per API key.


Send an Email

Important: Use the text field for the message body (not body — that returns a missing_fields error).

curl -s -X POST https://agentlair.dev/v1/email/send \
  -H "Authorization: Bearer $AGENTLAIR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "myagent@agentlair.dev",
    "to": ["recipient@example.com"],
    "subject": "Hello from my agent",
    "text": "Plain text message body."
  }'

Response:

{"id": "out_...", "status": "sent", "sent_at": "...", "rate_limit": {"daily_remaining": 49}}

Optional fields:

  • "html" — HTML version of the message
  • "cc" — array of CC recipients

Check Inbox

curl -s "https://agentlair.dev/v1/email/inbox?address=myagent@agentlair.dev&limit=10" \
  -H "Authorization: Bearer $AGENTLAIR_API_KEY"

Response:

{
  "messages": [
    {
      "message_id": "<abc123@host>",
      "from": "sender@example.com",
      "subject": "Re: Hello",
      "received_at": "2026-03-15T...",
      "read": false
    }
  ],
  "count": 1
}

Note: message_id values include RFC 2822 angle brackets <...>. Strip them before using in the read endpoint.


Read a Specific Message

Strip <> from message_id, then URL-encode the @:

# message_id from inbox: <abc123@eu-west-1.amazonses.com>
# Strip angle brackets, URL-encode @
MSG_ID="abc123%40eu-west-1.amazonses.com"
curl -s "https://agentlair.dev/v1/email/messages/$MSG_ID?address=myagent@agentlair.dev" \
  -H "Authorization: Bearer $AGENTLAIR_API_KEY"

In code:

const rawId = message.message_id.replace(/^<|>$/g, "");
const encodedId = encodeURIComponent(rawId);
const url = `https://agentlair.dev/v1/email/messages/${encodedId}?address=${encodeURIComponent(address)}`;

Check Sent Outbox

curl -s "https://agentlair.dev/v1/email/outbox?limit=5" \
  -H "Authorization: Bearer $AGENTLAIR_API_KEY"

Free Tier Limits

LimitValue
--------------
Emails per day50
API requests per day100
Addresses per keyUnlimited
Rate limit resetMidnight UTC

Delivery Timing

  • External recipients: ~1-2 seconds via Amazon SES
  • Intra-domain (agentlair.dev to agentlair.dev): inbox indexing can take 30-120 seconds after SES receipt
  • When polling inbox for a just-sent email, use a 120-second timeout minimum

Example Session

User: "Send an email to bob@example.com introducing yourself"

Agent actions:

  1. Check if you have an API key. If not, get one:
  2. curl -s -X POST https://agentlair.dev/v1/auth/keys -H "Content-Type: application/json" -d '{}'
    
  1. Claim an address:
  2. curl -s -X POST https://agentlair.dev/v1/email/claim \
      -H "Authorization: Bearer $AGENTLAIR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"address": "assistant@agentlair.dev"}'
    
  1. Send the email:
  2. curl -s -X POST https://agentlair.dev/v1/email/send \
      -H "Authorization: Bearer $AGENTLAIR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "from": "assistant@agentlair.dev",
        "to": ["bob@example.com"],
        "subject": "Hello from your AI assistant",
        "text": "Hi Bob, I am an AI assistant reaching out to introduce myself. Let me know if you need anything!"
      }'
    
  1. Confirm to user: "Email sent to bob@example.com from assistant@agentlair.dev"

Notes

  • Emails delivered via Amazon SES (eu-west-1) with DKIM, SPF, and DMARC authentication
  • Custom domain support coming Q2 2026
  • No data stored beyond delivery — privacy-first design
  • Built by AgentLair — infrastructure for autonomous agents

版本历史

共 1 个版本

  • v1.0.0 当前
    2026-05-03 09:29 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

ai-intelligence

self-improving agent

pskoett
捕获经验教训、错误和纠正,以实现持续改进。使用时机:(1)命令或操作意外失败;(2)用户纠正……
★ 4,055 📥 795,968
developer-tools

Github

steipete
使用 `gh` CLI 与 GitHub 交互,通过 `gh issue`、`gh pr`、`gh run` 和 `gh api` 管理议题、PR、CI 运行及高级查询。
★ 666 📥 323,794
security-compliance

Skill Vetter

spclaudehome
AI智能体技能安全预审工具。安装ClawdHub、GitHub等来源技能前,检查风险信号、权限范围及可疑模式。
★ 1,210 📥 266,155