> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Let AI Agents Send Email With Resend

> Let agents send transactional email and check delivery status with Resend. The gateway injects your API key, so agents never see or leak it.

## Overview

Buckle connects AI agents to Resend using an API key. Agents can send transactional emails, check delivery status, and manage contacts. The gateway injects the API key into requests to the Resend API automatically.

This is useful for agents that need to send notifications, alerts, or reports by email without configuring SMTP.

## What you will set up

* A Resend API key with sending or full access
* Automatic key injection on Resend API requests
* Per-agent, per-tool access, such as rate limits on sends

## Setup

**1. Create an API key in Resend**

Go to [resend.com/api-keys](https://resend.com/api-keys) and create a new API key. Choose the appropriate permission level (sending access or full access). Copy the key.

**2. Connect in Buckle**

Open the Buckle dashboard, go to **Settings** > **Apps** > **Resend**, and paste your API key.

![Buckle connect window for Resend, showing the setup guide link and the fields to fill in.](https://mintcdn.com/onecli-17d3f772/h1DTAVlDkLshz4JZ/images/integrations/resend/buckle-connect-resend.png?fit=max\&auto=format\&n=h1DTAVlDkLshz4JZ\&q=85\&s=a5f74f33e650d8af9d05352de2ec69f4)

The Resend connect window in Buckle.

## What agents can do

* Send emails with specified from address, recipients, subject, and HTML or plain text body
* Send emails with attachments
* Check the delivery status of a sent email (delivered, bounced, complained)
* List sent emails and their statuses
* Manage contacts and audiences (create, list, update, delete contacts)
* Send batch emails to multiple recipients
* Use verified domains for sending

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access.md) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization [rules](/docs/guides/rules.md) add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Resend.

## FAQ

> [accordion] How do I rotate my Resend API key?
>
> Create a new key at [resend.com/api-keys](https://resend.com/api-keys), then paste it into **Settings** > **Apps** > **Resend**. Agents pick it up automatically. Then delete the old key.

> [accordion] How do I keep the key out of the agent's context?
>
> Don't set `RESEND_API_KEY` in the agent's environment. Store it in Buckle, and the gateway injects it at the proxy. See [How it works](/docs/how-it-works.md).

> [accordion] Can I limit how many emails an agent sends?
>
> Yes. Add a rate limit with [rules](/docs/guides/rules.md), or put sending behind approval when you [grant](/docs/guides/agent-access.md) the connection.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.