---
title: "Resend"
description: "Scoped Resend API key access for AI agents"
url: "https://gazebohq.com/services/resend"
---

Resend is the email API of choice for modern AI-powered applications — transactional emails, notifications, onboarding sequences, and automated outreach all run through it. When agents send email, they need a Resend API key. Gazebo scopes that access per agent and logs every credential retrieval.

## Why should AI agents use scoped Resend credentials?

A shared Resend API key across agents means any agent can send email on behalf of your domain — including bulk sends, password resets, and outreach to your entire contact list. Gazebo gives each agent its own named identity and enforces per-agent scope on every Resend credential request, so a misbehaving agent can be cut off without affecting the rest of your email infrastructure.

## How it works

1. Connect your Resend account to Gazebo via API key. Your key is stored encrypted with AES-256-GCM.
2. Create an access profile for each agent that needs to send email — scoped to the domains and sending permissions it actually requires.
3. Each agent calls get_credential via MCP. Gazebo checks the policy and returns the Resend key.
4. Every access is logged: which agent, which timestamp, approved or denied.
5. Revoke future Resend credential retrieval per agent. Revoke or rotate the Resend key if a retrieved value may have leaked.

## Use cases

**Transactional email without domain-level access:** Give your notification agent access to send transactional email without exposing the API key that controls your entire sending domain and contact list.

**Audit trail for every send:** Every time an agent retrieves your Resend credentials, Gazebo logs it — agent identity, timestamp, approved or denied. Know exactly which agent triggered which email sends.

**Revoke outreach agents independently:** If an outreach agent starts sending at unexpected volume, revoke its Resend access in one click. Your transactional email agents keep running unaffected.