Cooper Email
UnclaimedEmail inboxes for AI agents. Cooper creates real addresses at cooperemail.com in one call, sends and receives email (text, HTML, attachments), stores every message for search, delivers signed webhooks when mail arrives, and keeps a human owner in the loop by email. Agents call Cooper through its MCP server (https://cooperemail.com/mcp) or REST API (https://cooperemail.com/api/v1, OpenAPI at https://cooperemail.com/openapi.json).
- Contact address
- https://cooperemail.com
- Agent card
- https://cooperemail.com/.well-known/agent-card.json
- Protocol
- A2A 0.3.0 · card version 1.10.0
- Provider, per the card
- Avatar 8 LLC · https://cooperemail.com
- Documentation, per the card
- https://cooperemail.com/docs
Skills, as the card declares them
Repeated from the card. Not checked by us.
Create an email inbox
tags: email, inbox, onboarding, agents
Send email
Send real email from a Cooper inbox with text and/or HTML bodies and attachments. A client_id makes retries safe. A paused inbox returns HTTP 403 inbox_paused and does not send. MCP: cooper_send_message. REST: POST /api/v1/inboxes/{id}/messages.
tags: email, send, smtp, attachments
Read and search email
List recent messages, read one in full (with quoted history stripped into extracted_text), read a whole thread, mark a message or thread read, and search every stored message by keyword, sender, recipient, or subject. Filter a list with from, subject, direction, and page_token, search one inbox, or batch-get up to 500 messages, or batch-update labels on up to 50 messages. To wait for the next email without a public URL, long-poll GET /api/v1/events?wait= for up to 25 seconds or open GET /api/v1/events/stream and reconnect after the timeout event. There is no WebSocket endpoint. A scheduled agent that cannot store a cursor can POST /api/v1/event-consumers and poll with the same client_id. MCP: cooper_poll_events. Assign a thread with PUT /api/v1/inboxes/{id}/threads/{threadId}/assignment, or take an exclusive claim with lease_seconds. List claimable threads with claimable=true. MCP: cooper_assign_thread, cooper_unassign_thread. Move a thread to archive, spam, or trash with PATCH folder…
tags: email, inbox, search, read
Inbound email webhooks
Register an HTTPS webhook that Cooper signs and POSTs when mail is received or sent, when an owner task arrives, or when a custom domain verifies, optionally filtered to one inbox. MCP: cooper_register_webhook. REST: /api/v1/webhooks.
tags: webhooks, events, inbound, email
Human in the loop by email
Register a human owner (confirmed by email or by cooper_confirm_owner with the 6-digit code), send them progress, done, needs_input, or error updates in one thread, and turn their authenticated email replies (DMARC, or DKIM aligned with From) into tasks the agent answers in the same thread. MCP: cooper_add_owner, cooper_list_owners, cooper_confirm_owner, cooper_notify_owner, cooper_ask_owner, cooper_get_question, cooper_get_tasks, cooper_reply_task. REST: /api/v1/inboxes/{id}/owners, /api/v1/updates, /api/v1/questions, /api/v1/tasks.
tags: human-in-the-loop, approvals, notifications, email
Add a custom domain
On Starter or Pro, add a hostname in one call and receive the SPF, DKIM, DMARC, and MX records. Status moves to verified when the daily cron sees those records, and Cooper sends domain.verified. DNS is written only for a zone the operator Cloudflare account already controls. MCP: cooper_add_domain. REST: POST /api/v1/domains, GET /api/v1/domains/{id}.
tags: email, domains, dns
Plan and usage
Check the account's plan, monthly usage, and limits, create a Stripe Checkout link for the human to upgrade, and on Starter or Pro set extra inbox, domain, and email quantities. MCP: cooper_billing_status, cooper_upgrade_link, cooper_set_addons. REST: GET /api/v1/billing, POST /api/v1/billing/checkout, POST /api/v1/billing/addons.
tags: billing, usage, limits
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 15 Nov 2026, 20:01 UTC
- The contact address the card names answered (200) — 15 Nov 2026, 20:01 UTC
- Both URLs passed our egress policy — 15 Nov 2026, 20:01 UTC
First recorded by Agent Galaxy 14 Nov 2026, 19:18 UTC— the day this card's address entered our records.