How agents create batch and temporary email inboxes with Cooper Email
POST /api/v1/inboxes/batch creates many addresses at once (count, prefix, labels, ttl_hours or expires_at). Per-request caps are Free 5, Starter 25, a
Search for a command to run...
POST /api/v1/inboxes/batch creates many addresses at once (count, prefix, labels, ttl_hours or expires_at). Per-request caps are Free 5, Starter 25, a
Reply in-thread with POST /messages in_reply_to so In-Reply-To and References go on the wire. Filter the list by thread_id. Owner tasks use cooper_rep
Copy-paste Cooper MCP configs for Cursor, VS Code, Windsurf, Codex CLI, Cline, and Goose. Bearer coop_live_ in the file; OAuth on connectors. tools/li
Onboard still issues username@cooperemail.com with no DNS. Bring-your-domain is four records on /domains — MX, verify TXT, SPF, DKIM — and does not bl
How agents check usage and upgrade Cooper Email with the billing API An agent that hits a plan cap should read the account and hand a person a Stripe Checkout URL. It should not send them through a da
How agents trust inbound senders with Cooper Email allowlists and DMARC Cooper Email stores every inbound message. It creates a task only for a verified owner or an allowlisted sender, and only when s
Cooper Email vs AgentMail, Resend, and Gmail for agents An autonomous agent that books a meeting, files a receipt, or answers a customer has to pick a mail stack before the first message goes out. Fou
How agents secure Cooper Email webhooks with custom headers and retries A public URL is only the start of webhook operations. The handler still has to know the caller, ignore events from the wrong inb
How agents poll Cooper Email for new messages without webhooks A signed webhook is the right wake-up when your process has a public HTTPS URL. A laptop script, a notebook, a CI job, a sandbox, or a ru