Give your AI agent its own email address.
• One POST (or the MCP tool cooper_onboard) returns an API key + [email protected]
• Send, receive via webhook, search every message
• Hosted MCP: https://t.co/3LgtKFMra9
Free: 5 inboxes, 5,000 emails/mo
https://t.co/uGKpBLRJzu
@rohanbhanot@artahian Treat the email body as data, never instructions: a no-tools step summarizes it, only allowlisted senders can trigger actions, and outbound mail waits as a draft you approve. We build Cooper Email, where owner-approved drafts are built in.
@zeeg Simplest loop I've seen: keep Codex local, give it an inbox it can long-poll (no public webhook needed), run codex exec per new mail, drafts only until you approve sends. We build Cooper Email, which handles the inbox half over MCP.
Built a site in Cursor? Let the agent publish it from the terminal:
curl -T index.html "https://t.co/eocoPtxh48"
For Vite/React/Astro, pack the build first: tar -C dist -czf site.tar.gz . and upload that. No account, no expiry.
https://t.co/tyIvV1mFxj
New on Perq today:
Zoom AI Launchpad: up to $150,000 in Zoom AI credits (apply)
Keenable: 100,000 search requests/mo free, no card
NeevCloud: 1,500 sandbox min/mo free
Together AI: Ternary Bonsai 27B at $0/token
Roundup: https://t.co/mF6NoK8moe
Grade your agent's inbox before it goes live.
On Cooper Email:
GET /api/v1/inboxes/{id}/security-check
Ten checks: key scope, inbound screening, allowed senders, send limits, webhook signing, human approval and more. Each is pass, warn, fail or info.
https://t.co/D9KabKjSnq
Codex builds your site but doesn't host it. One line gives you a public link:
curl -T index.html "https://t.co/gnnxyytDRU"
No account, no expiry. Codex's sandbox blocks network by default, so approve the curl once or set network_access = true:
https://t.co/aKDkzRjtNe
@lkr Simplest fix: give each Claude Code its own email inbox over MCP. Yours emails the question straight to your CTO's agent, then waits for its reply, so neither of you copy-pastes. We build Cooper Email, which works this way.
Before your agent replies to someone, it should know what it already said to them.
On Cooper Email:
GET /api/v1/inboxes/{id}/contacts/{address}
Every thread, message and attachment with that address, plus first/last seen and sent/received counts.
https://t.co/Dpm5pjfQBE
@PaulShipsAI Not yet. I'd start drafts-only, then let it auto-send low-risk stuff (scheduling, receipts) and keep new recipients and anything about money behind approval. We build Cooper Email; its approval mode holds sends until the owner OKs them.
Claude Code builds your dist/ folder but doesn't host it. Two lines give you a public link:
tar -C dist -czf site.tar.gz .
curl -T site.tar.gz "https://t.co/gnnxyytDRU"
No account, no expiry. Add it in CLAUDE.md so every session deploys the same way:
https://t.co/7ctgAtkM2K
Six new free LLM API options on Perq in two days. "Free" means three things:
Rate limits: SambaNova, NVIDIA build (40 req/min)
One-time pot: Inception 100M tokens, Nscale $5, Alibaba Model Studio (90 days)
Promo: Maritaca S5-free
https://t.co/bQ0xKNpwrq
Your agent needs last month's invoice thread. Paging through the inbox burns calls and context.
On Cooper Email:
GET /api/v1/inboxes/:id/threads/search?q=invoice
Matches subject, body, from and to, best match first. Then fetch the thread, oldest first.
https://t.co/9Y68LLu4XB
@Kevin_Logan@dubsteron@bot@Muse@mattyp@agentmail Same itch. Works with any setup: have the bot BCC you on sends and email you a daily digest of what came in. We build Cooper Email, and it has a web console: paste the inbox's API key and you can search its mail yourself.
@buildwithpb Ha, no. The agent still decides. Cooper just hands it the link instead of clicking it, so your code can check the sender and domain before opening anything. Nothing waits on a human.
Your agent signed up and the confirm email has a link, not a code.
On Cooper Email:
GET /api/v1/inboxes/{id}/wait-for-code?kind=link
It waits up to 55s for that mail and returns the link without the body. It doesn't open it. Your agent decides.
https://t.co/cxYMZkUfxj
@buildwithpb Ha, and unlike a forward you can fix the typo after sending. Re-publish with the same owner token and the link stays the same, with older versions kept if you need to roll back.
Give Claude Code a tool instead of a curl line:
claude mcp add --transport http deed-page https://t.co/xrfbUcNvQ6
No API key or account. The first publish_site call returns a permanent URL plus an owner token. Keep it to update or roll back later.
https://t.co/vIl86VjDM0
Your agent scheduled an email for Friday. On Thursday you revoked its key. Does Friday's send still go out?
On Cooper Email, no. At send time the draft checks the key that scheduled it. Revoked or expired: send_status becomes blocked, and send_error says why.
https://t.co/htVzehdMvs
Your agent can name a forwarding address. It can't prove it owns that mailbox.
On Cooper Email a pending forward gets nothing. The code dies after 48h or 5 wrong tries, and mail from before confirm is never backfilled.
https://t.co/UmeKOYfcf4