Resend gives every agent an email address and Adyen gives every coding tool the same skills
Two developer-infra launches on October 22 fix boring, real problems that show up the moment agents leave the demo.
Resend, the email API company, launched Inboxes. An inbox sends and receives mail at an address on your own domain, groups every message into a thread, and exposes each thread to your app, your team and your agents through the same API. The headline use case is giving each agent its own address to receive tasks, approvals and updates, with people and agents working the same inbox side by side. It ships with folders, Gmail-style search, labels, drafts, forwarding with idempotency keys, webhooks for events like a thread being assigned, and settings for a built-in agent's instructions and tone. Link: https://resend.com/blog/announcing-inboxes
Email is an underrated agent interface. Every vendor, customer and colleague already has it, it leaves a written trail, and an approval by reply is something a human can do from a phone. Giving an agent its own address also gives it something it badly needs: an identity that is not a person's account. After a week of stories about agents logging into banks as their users, that is not a small thing.
Adyen, the payments company, open-sourced Agent Marketplace under Apache 2.0 the same morning. It is a CLI for platform teams: publish instructions and skills once, keep one config file as the source of truth, and it translates them into each coding tool's own format and location, regenerating everything in one command. Adyen says it is an internal tool shared, not a product. Link: https://www.adyen.com/knowledge-hub/agent-marketplace
The fact that a payments company had to build this tells you how fragmented agent config still is. Every harness wants its own rules file in its own folder. AGENTS.md and the Agent Skills standard, which moved to the Agentic AI Foundation the same day, are the slow fix. Adyen's tool is the fix you can run this afternoon.
← Back to all articles
Resend, the email API company, launched Inboxes. An inbox sends and receives mail at an address on your own domain, groups every message into a thread, and exposes each thread to your app, your team and your agents through the same API. The headline use case is giving each agent its own address to receive tasks, approvals and updates, with people and agents working the same inbox side by side. It ships with folders, Gmail-style search, labels, drafts, forwarding with idempotency keys, webhooks for events like a thread being assigned, and settings for a built-in agent's instructions and tone. Link: https://resend.com/blog/announcing-inboxes
Email is an underrated agent interface. Every vendor, customer and colleague already has it, it leaves a written trail, and an approval by reply is something a human can do from a phone. Giving an agent its own address also gives it something it badly needs: an identity that is not a person's account. After a week of stories about agents logging into banks as their users, that is not a small thing.
Adyen, the payments company, open-sourced Agent Marketplace under Apache 2.0 the same morning. It is a CLI for platform teams: publish instructions and skills once, keep one config file as the source of truth, and it translates them into each coding tool's own format and location, regenerating everything in one command. Adyen says it is an internal tool shared, not a product. Link: https://www.adyen.com/knowledge-hub/agent-marketplace
The fact that a payments company had to build this tells you how fragmented agent config still is. Every harness wants its own rules file in its own folder. AGENTS.md and the Agent Skills standard, which moved to the Agentic AI Foundation the same day, are the slow fix. Adyen's tool is the fix you can run this afternoon.
Comments