Give Your AI Agent an Email Inbox

Connect an AI agent to a Resend inbox to triage email and draft replies.

Introduction

30 Second Summary

A conversation only works when both sides can read what comes back. A one-way assistant leaves every reply waiting for a person to pick it up.

In this project, you will create a Resend Inbox at an address on your domain. You will send it real email before connecting a coding agent through MCP or the Resend API to triage the thread and draft a reply for your approval.

What You'll Build

When you demo the finished workflow, a real email becomes a labelled thread with a reply draft waiting for your approval.

By the end of this project, you'll have:

A working inbox that receives messages at an address on your domain. You'll see each message grouped into a thread in the Resend dashboard.
An API inbox check that returns the same thread as JSON. You can compare the response with the thread in the dashboard.
An agent-assisted email flow that labels incoming mail and summarises each request. You'll approve a reply draft before sending it inside the original conversation.
An optional Secret Mission to push your skills further.

Are there any prerequisites?

You'll need access to a domain you control because your inbox address lives there. Your test setup also includes a personal email account plus a coding agent with MCP or API access.

Before We Start

The first Resend Inbox cannot receive a useful test if one of its supporting tools is missing. Domain access is the prerequisite most likely to slow down your progress.

This step confirms access to your domain. It also checks your personal mailbox.

Finally, you will prepare your coding agent. You will verify curl from a terminal before any Resend configuration begins.

In this step, get ready to:

Confirm your email prerequisites.
Prepare a coding agent with MCP support.
Verify curl from your terminal.

Confirm your email prerequisites

Your inbox address will live on a domain you control. A personal email account will act as the outside sender during testing.

Domain controls can be a little fiddly because each provider organises them differently. You only need to prove that you can manage the domain at this stage.

Choose a domain that you can use for this project.
Sign in to the provider account that manages the domain.
Open the management page for that domain.
Confirm that you can change the domain's records.
Sign in to the personal email account you will use for testing.
Send a short test message from the personal email account to the same address.
Refresh the personal inbox.

You should see the test message in the inbox. This proves that the account can send the original message and receive the reply later.

Don't have a domain yet?

Buying a domain is a paid action, so this is the point to slow down before checkout.

Choose a domain provider you trust.
Review the displayed price before checkout.
Complete the purchase only when the total fits your budget.
Return to this step after the domain appears in your provider account.

Prepare an MCP-capable coding agent

Your coding agent will use MCP to connect to the inbox later. Support for MCP is the key requirement at this stage.

Choose the tab that matches your current coding agent setup.

✔️ My coding agent supports MCP

Check your coding agent's official documentation for MCP support.
Launch your coding agent.
Sign in if the agent asks you to authenticate.
Start a new agent session.

You should reach a session where you can enter a prompt. Your agent is ready for the inbox connection later.

Can't start an agent session?

Confirm that your internet connection is working. Check that your account can access the agent.

If the session still does not open, ask for targeted help: Help me start a new session in my coding agent.

ⓧ I need an MCP-capable coding agent

Cursor is one coding agent with documented MCP support. You can use its desktop application for this project.

Visit Cursor's official download page.
Download the installer for your operating system.
Open the downloaded installer.
Follow the installation prompts for your operating system.
Open Cursor from your applications menu.
Sign in when prompted.
Confirm Cursor's MCP support in the official MCP documentation.

That is one important dependency sorted. You should now see a Cursor session where you can enter a prompt.

Cursor won't open?

Confirm that you downloaded the installer for your operating system. Reopen the installer if the application does not appear in your applications menu.

For help with your specific computer, ask: Help me finish installing Cursor.

Verify curl in your terminal

The curl command sends HTTP requests from a terminal. You will use it later to ask the inbox API for its threads.

Use your computer's application search to open a terminal.

Before you run the check, do you expect to see curl's version information or a missing-command message?

Check whether curl is installed by running this command:

curl --version

What does this command do?

The --version option asks curl to describe the installed command.
The output includes the curl version.
The output also lists supported protocols and features.

✔️ I see curl version information

Your terminal shows curl's version plus its supported protocols and features. That is your command-line API tool ready for the project.

ⓧ The curl command is missing

Your terminal needs curl before you can make the inbox API request. Use curl's official package list to find the installation option for your operating system.

Visit the official curl download page.
Select the package for your operating system.
Follow the package's installation instructions.
Close your terminal after the installation finishes.
Reopen your terminal from your computer's application search.
Verify the installation by running this command:

curl --version

What does this check prove?

This command asks the new curl installation to report its version. A version response proves that your terminal can find the command.

You should now see curl's version plus its supported protocols and features.

Still missing curl?

Confirm that you installed the package for your operating system. Restarting the terminal lets it detect newly installed commands.

If curl is still unavailable, ask for help: Help me make curl available in my terminal.

Your starting kit is ready. Next up, you will create your Resend account before building the inbox.

Create Your Resend Inbox

Your agent needs a real destination before it can receive a request. Resend turns an address on your domain into an inbox that stores each conversation.

This step gives your agent its own mailbox on the free plan. You'll verify the domain for inbound mail before creating the address your agent uses.

In this step, get ready to:

Create a Resend account on the free plan.
Configure your domain for receiving email.
Create the inbox address agent@your-domain.com.

Create your Resend account

The Resend Free plan includes up to three inboxes. This project uses one.

The sign-up flow may send you to an authentication provider for approval. Resend returns you to the dashboard after authentication finishes.

Open the Resend sign-up page in your browser.
Choose one of the authentication options shown on the page.

Approve any provider authorization prompt that opens in your browser.
Complete any email verification Resend requests.

You'll return to Resend after your identity is confirmed.

Continue until the Resend dashboard loads.

You're signed in. Your new Resend workspace is ready on the Free plan.

Configure your inbound domain

Resend verifies your control of the domain through DNS records. Receiving also needs an MX record that routes incoming messages to Resend.

Protect Existing Mail Delivery

Adding Resend's receiving MX record to a domain that already handles mail can disrupt delivery. Use a project domain whose inbound routing you can safely hand to Resend.

DNS setup is the fiddliest part because each provider arranges records differently.

Record the domain you will connect: your-domain.com.
Select Domains in the Resend dashboard.

You'll see the page Resend uses to manage verified domains.

Click Add Domain.

You'll see the form for connecting a domain to Resend.

Enter your-domain.com as the domain.
Select the region closest to you.

The form now identifies the domain Resend needs to verify.

Submit the domain form.

You'll land on the domain's Records tab. Resend generates the DNS records required for verification.

Open your domain's DNS provider in a second browser tab.
Sign in to the account that manages your-domain.com.

You'll see the DNS records that currently control your domain.

Add every record generated on Resend's Records tab with the exact values shown.
Save the DNS changes in your provider.

You'll see the new records in your provider's DNS table.

DNS verification can feel slow. Most domains verify within 15 minutes. Global propagation can occasionally take up to 72 hours.

Return to the domain details page in Resend.
Wait for the domain status to change to verified.

Your verified status proves that Resend recognizes the domain as yours.

Turn on Receiving in the domain details page.

You'll see a modal containing the MX record that routes incoming email to Resend.

Copy the MX record exactly as Resend displays it.
Return to your DNS provider.

You'll see the DNS record list for your domain again.

Add the copied MX record with the exact values shown by Resend.
Save the new MX record.

You'll see the receiving MX record in your provider's DNS table.

Return to the receiving modal in Resend.
Click I've added the record.

Resend begins checking the public DNS record for your receiving route.

Wait for the receiving record to show as verified.

That's the fiddly setup complete. Your domain is now available for receiving email through Resend.

Domain Still Pending?

Compare every DNS record with the values on Resend's Records tab.
Use Restart verification after 72 hours of a Pending status.
Ask for help with your DNS records: Help me diagnose why my Resend domain or receiving MX record is still pending.

Create the agent inbox

An inbox turns your verified domain into a specific email address. Resend stores messages sent to that address as conversation threads.

Select Inboxes in the Resend dashboard.
Click Create inbox.

You'll see the form for choosing the inbox address.

Enter agent as the part before the at sign.
Choose your-domain.com from the verified domain list.

The form now represents the full address your agent uses.

Submit the inbox form.

You'll see the new inbox appear in Resend.

Record the full address Resend displays: agent@your-domain.com.

Picture the exact address Resend should show before you check the inbox list.

Select Inboxes in the dashboard sidebar.

You'll see agent@your-domain.com listed as an available inbox.

You did it. Your agent now has a real mailbox on your domain.

Inbox Missing from the List?

Refresh the Inboxes page.
Confirm that the selected domain shows verified sending records.
Get help with the missing inbox: Help me work out why agent@your-domain.com is missing from my Resend Inboxes page after I submitted the form.

✔️ My inbox is ready

Great. Your Resend account is active. Your inbound domain is configured. Your agent inbox is visible in the dashboard.

ⓧ I'd like to double check the setup

Inbound Domain: Configured in Resend for your-domain.com and available for receiving email.

Resend Account: Created and signed in on the free plan.

Resend Inbox: Created with address agent@your-domain.com and visible in the Resend dashboard.

Your agent has an address that can receive real email. Next up, you'll send it a message from your personal account.

Send a Test Email

The inbox address is ready in Resend. Now you can give it its first real message from outside the dashboard.

An empty inbox only proves the address exists. A message from your personal account proves that inbound delivery works.

Success is a new dashboard thread. It shows your test subject and body.

In this step, get ready to:

Send a test message from your personal email account.
Confirm the incoming message appears as a thread in your Resend inbox.

Send a message to your inbox

A message from another email account tests the full delivery path to your inbound domain. The recipient must match the inbox address you created earlier.

Go to your personal email account.
Start a new email.
Set the recipient to agent@your-domain.com.
Set the subject to Inbox test.
Enter Hello, this is a test message for my agent inbox. in the message body.
Send the message.

What does this test prove?

The message starts outside Resend. It reaches the address through your configured inbound domain.

Resend groups the message into a thread. The thread keeps the sender information with the subject and body.

Confirm the incoming thread

The dashboard provides visible proof that Resend accepted the message. The newest thread should match the email you just sent.

Switch back to the Resend dashboard from earlier.
Select the inbox with the address agent@your-domain.com.

Before you open the newest item, what subject do you expect the incoming thread to show?

Open the newest incoming thread.

You should see a thread from your personal email account with the subject Inbox test.

Open the thread to confirm the body says Hello, this is a test message for my agent inbox..

That is your first live delivery. Your Resend inbox can now receive real mail from outside the dashboard.

Cannot find the test thread?

Compare the email recipient with agent@your-domain.com to catch any spelling differences.
Check the delivery status in your personal email account.
Refresh the inbox thread list.

Help me troubleshoot a test email that is missing from my Resend inbox.

Your inbox has received its first real message. Next, you will retrieve this same thread through the API and inspect its structured data.

List Inbox Threads with the API

Your test email is waiting in the inbox you created with Resend. The dashboard confirms that the conversation arrived.

A coding agent needs the same thread as structured data before it can triage the request. You will authenticate an API request with a Resend API key. Then curl retrieves the thread list as JSON.

In this step, get ready to:

Create a Resend API key with permission to read inbox threads.
Authenticate a curl request to the inbox threads endpoint.
Match the returned JSON to your test email thread.

Create an API key

An API key proves that your request belongs to your Resend account. The thread-listing request needs Full access because that permission includes read operations.

Protect This API Key

This credential has broad access, so keep its value on your device throughout this step. Resend displays the value only once after creation.

Return to the Resend dashboard from earlier.
Select API Keys in the left sidebar.
Click Create API Key.
Enter Inbox Thread Reader in the Name field.
Select Full access under Permission.
Submit the form to create the key.
Copy the API key as soon as Resend displays it.

You now have the credential that lets curl read the inbox. That connects your terminal to the same threads you see in the dashboard.

Can't Create the API Key?

Confirm that the form has a name and a selected permission. If the creation control stays unavailable, refresh the dashboard before completing the form again.

Ask for help with the account-specific details here: Help me create a full-access Resend API key for listing inbox threads.

List inbox threads with curl

The list endpoint accepts an inbox email address and returns its most recently active threads first. Each thread summary includes details such as its subject, sender, recipients, read state, and folder.

Before you run the request, do you expect the returned thread details to match the email you saw in the dashboard?

Retrieve the threads by running this command after replacing your-api-key-here with the API key you copied:

curl -X GET 'https://api.resend.com/inboxes/agent@your-domain.com/threads' \
     -H 'Authorization: Bearer your-api-key-here'

What Does This Command Do?

The GET request asks Resend for existing thread summaries.
The URL selects the inbox at agent@your-domain.com.
The Authorization header sends your API key as a Bearer token.

You'll see a JSON object with object set to list. Its data array contains the inbox threads.

Find the thread object whose subject matches your test email.
Confirm that its from value matches your personal email account.
Confirm that its to array includes agent@your-domain.com.

That closes the gap between the dashboard and the API. Your test conversation is now available as structured data that an agent can process.

Request Not Returning Your Thread?

Confirm that you replaced the entire your-api-key-here placeholder without removing the surrounding header text.
Check that the API key uses Full access.
Check that the URL contains the exact inbox address agent@your-domain.com.
Get focused debugging help here: Help me debug my inbox thread request.

✔️ I Found My Test Thread

Your JSON response includes the same test email thread shown in the Resend dashboard. Keep the API key private for the next step.

ⓧ I'd Like to Double Check the Request

Compare your request with this reference. The inbox address and endpoint should match exactly.

curl -X GET 'https://api.resend.com/inboxes/agent@your-domain.com/threads' \
     -H 'Authorization: Bearer your-api-key-here'

Confirm that your API key was created or obtained for this session.
Confirm that the response is a JSON list.
Confirm that the list includes the test email thread from your personal account.

Your inbox can now be read through code. Next, you will connect your coding agent through MCP so it can triage the same conversation.

Connect Your Coding Agent

Your test message already appears in the Resend dashboard. That proves the inbox can receive email from the outside world.

Your coding agent still needs a secure route into that inbox. You will provide that route through the Model Context Protocol (MCP).

In this step, get ready to:

Add Resend's hosted MCP server to your coding agent.
Approve the connection through OAuth.
Verify that the agent can read the test thread.

Add Resend's remote MCP server

Resend hosts an MCP server that exposes inbox tools to compatible agents. The hosted server runs remotely, so your computer does not need to run another process.

Return to your coding agent from earlier.
Open its settings area.
Search those settings for MCP.
Select the control for adding a remote MCP server.
Enter resend as the connection name.
Paste https://mcp.resend.com/mcp into the server URL field.
Choose Streamable HTTP as the transport if your client requests one.
Save the connection.

Your agent now knows where to find Resend's hosted MCP tools. Saving the server starts the authorization flow when the client first contacts Resend.

Why use the hosted server?

The hosted server provides inbox tools through one remote endpoint. It can list inboxes, search threads, read thread emails, and manage drafts.

This project begins with a read check. That keeps the first test focused on proving access to the existing thread.

Authorize the connection with OAuth

OAuth lets your Resend account approve the MCP connection through a browser. Your existing API key stays out of the agent's chat and configuration.

Giving an agent access to email can feel sensitive. The authorization screen lets you confirm the Resend account before access is granted.

Start the new resend connection from your coding agent.
Switch to the browser window opened by your client.
Continue with the Resend account from earlier.
Review the access request.
Approve the connection.
Return to your coding agent.

Your coding agent should now show the resend server as connected. The Resend inbox tools are now available to the agent.

What is OAuth doing?

OAuth records your approval without exposing your API key to the coding agent. Resend associates that approval with the MCP connection.

You stay in control of the grant through your Resend account settings. The next check confirms that the grant can reach your inbox.

Did the browser stay closed?

Check your coding agent's MCP status for an authorization link.
Allow the browser to open external links from your coding agent.
Reconnect the resend server after confirming the URL is https://mcp.resend.com/mcp.
Ask for targeted help with the connection: Help me complete OAuth for the Resend remote MCP server in my coding agent.

Verify access to the inbox

A connected status confirms that the server responded. A successful thread read proves that the agent can reach the inbox you created.

Before you send the prompt, do you expect the agent to find the same sender and subject shown in the Resend dashboard?

Send this read-only request to your coding agent:

Use Resend to list my inboxes. Find agent@your-domain.com. Read the newest thread in that inbox. Report the sender and subject. Do not change the thread. Do not draft or send a reply.

What does this check?

Listing the inboxes proves that the MCP connection can access Resend.
Reading the newest thread proves that the agent can use the inbox thread tools.
The final instructions keep the verification limited to reading.

Switch back to the Resend dashboard from earlier.
Return to the agent@your-domain.com inbox.
Compare the agent's sender and subject with the newest test thread.

Your agent should name agent@your-domain.com as the inbox. Its sender and subject should match the test email from your personal account.

That's the connection proven. Your coding agent can now read the same inbox thread that you can see in Resend.

Can the agent connect but not read?

Confirm that the agent reports the resend MCP server as connected.
Check that the inbox address in your prompt is exactly agent@your-domain.com.
Repeat the OAuth flow with the same Resend account that owns the inbox.
Ask for help without sharing your API key: Help me diagnose why my connected Resend MCP server cannot read my inbox threads.

Your agent now has verified read access to the inbox. Next, you will put that access to work while keeping control of what happens to the thread.

Triage the Inbox Thread

Your test email is visible in Resend. Your coding agent can read its thread through MCP.

A raw email still leaves you to work out what the sender needs. In this step, your agent produces a category plus a short summary for you to verify before any reply is drafted.

In this step, get ready to:

Ask your coding agent to triage the test email thread.
Review the assigned category plus summary.
Confirm the triage against the original message.

Ask the agent to triage the thread

Triage turns an incoming message into a decision-ready snapshot. The category tells you what kind of request arrived.

Switch back to the coding agent you connected to Resend earlier.
Enter the following prompt in the agent's chat:

Read the test email thread in the agent@your-domain.com inbox. Triage that thread only.

Assign one concise category based on the sender's request. Start your response with `Category:` followed by that category.

Write a two-sentence summary. Include the sender's requested action. Mention urgency only if the sender stated it.

Include the thread identifier. Do not draft or send a reply.

How Does This Prompt Guide the Agent?

The inbox address limits the task to the inbox you created earlier.
The category gives you a quick way to sort the request.
The summary captures the requested action without inventing urgency.
The final instruction keeps the reply workflow untouched for the next step.

Submit the prompt.
Wait for the agent to finish reading the thread.
Check that the response starts with Category:.
Check that the response includes the thread identifier.
Check that the summary contains two sentences.

You should see the test thread's identifier. You should also see one category plus a two-sentence summary of the sender's request.

Can't Find the Test Thread?

Confirm that the prompt names agent@your-domain.com exactly.
Confirm that the existing Resend connection still has inbox-reading access.
Ask the agent to identify the test thread from the incoming message sent by your personal email account.
Help me diagnose the agent's inbox access.

Verify the triage against the email

The original email is the source of truth for this check. Your review catches categories that are too broad plus summaries that add details the sender never provided.

Before you compare the two, do you expect the category to match the sender's actual request?

Return to the Resend dashboard from earlier.
Select agent@your-domain.com from the inbox list.
Select the test email thread from earlier.
Read the requested action in the original message.
Compare that action with the agent's category.
Compare the same action with the agent's summary.

You should see a category that matches the email's purpose. The summary should capture the sender's request without adding unstated urgency.

That is the triage loop working. Your agent has turned one email into a verified category plus summary while leaving the reply unsent.

Does the Triage Miss the Request?

Tell the agent which sentence in the thread contains the requested action.
Ask the agent to replace any category that does not match that action.
Ask the agent to remove any urgency that the sender did not state.
Help me correct this inbox triage result.

Your agent has now turned an email into a verified triage result. Next, you'll ask it to draft a reply that stays unsent until you approve it.

Draft and Send a Reply

Your coding agent has already triaged the test email. Now it needs to prepare a useful response.

An agent with access to your Resend inbox can prepare that response quickly. Human approval controls what leaves the inbox.

In this step, get ready to:

Create a reply draft inside the existing test email thread.
Review the draft before approving it for delivery.
Verify threaded delivery across both mailboxes.

Create a reply draft

A draft is a saved response that has not reached the recipient. It gives you a safe checkpoint before delivery.

Ask the coding agent from earlier to draft a concise response that addresses the sender's request.
Ask the agent to save that response inside the existing thread without sending it.

The agent should confirm that it saved a draft without sending it.

Switch back to the Resend dashboard from earlier.
Select the agent@your-domain.com inbox.
Open the triaged test email thread.

You'll see the agent-generated reply inside the same thread. Its draft state shows that the message has not been sent.

That is the safety checkpoint working: your agent has prepared a response while you still control delivery.

Draft missing from the thread?

Confirm that the agent targeted the existing triaged test thread.
Ask the agent to report whether its Resend connection permits draft creation.
Ask for help with the connection issue using this troubleshooting prompt.

Review and send the approved reply

Draft review protects the accuracy of your response. It also prevents the agent from releasing wording that you have not approved.

Read the draft from start to finish.
Compare the draft with the sender's original request.
Request corrections from the coding agent for any inaccurate wording.
Review the revised draft if you requested corrections.

This send is irreversible, so a careful pause here keeps you in control.

Before you approve the draft, do you expect the reply to stay in the existing conversation or start a separate conversation?

Tell the coding agent that you approve the current draft.
Ask the agent to send the approved reply from agent@your-domain.com within the existing test thread.
Switch back to the same Resend thread from earlier.

The coding agent should confirm that it sent the approved reply.

In the Resend thread, you'll see the outgoing message beneath the original email.

The important handoff is complete because your approval controlled the final send.

Reply still showing as a draft?

Confirm that the approved draft still belongs to the existing test thread.
Review the agent connection for permission to send mail from your inbox.
Get help with the failed send using this troubleshooting prompt.

Verify the threaded delivery

Threaded delivery is the final proof that the reply followed the original conversation. Checking both inboxes confirms the full route from agent approval to recipient delivery.

Before you check both places, where do you expect the reply to appear in each conversation?

Refresh the existing Resend thread.

You'll see the original incoming message followed by the sent reply.

Return to your personal email account from earlier.
Open the original test message.
Check the conversation for the reply from agent@your-domain.com.

You'll see the reply grouped beneath your original message. This confirms that the agent responded inside the existing thread.

Reply missing from your mailbox?

Refresh your personal mailbox once.
Check the spam folder for a message from agent@your-domain.com.
Confirm that the Resend thread shows the reply as sent.
Get help tracing the delivery using this troubleshooting prompt.

You now have a working agent inbox where every outgoing response passes through your approval before reaching the sender.

Secret mission

Build a Human Approval Policy

Your inbox agent can already triage messages and prepare replies. In this mission, you will define clear approval boundaries, test them against synthetic requests, and audit the reply you already sent without changing the inbox.

Clean Up Your Resources

Your single Resend Inbox fits within the free plan allowance of up to 3 inboxes. Keeping it adds no ongoing inbox charge while your account stays within that allowance.

Choose whether to keep the inbox active, disconnect agent access for now, or remove the resources created for this project.

Resources you used:

Resend inbox at agent@your-domain.com with its test email thread.
Inbound email domain your-domain.com configured in Resend.
Coding agent access through the Resend MCP server or API authorization.
Resend API key created for the session.

Keep everything running

No action needed. Choose this if you want the inbox and coding agent ready for more email workflows.

Your agent@your-domain.com inbox remains available for incoming mail.
Your your-domain.com inbound domain configuration remains available for the inbox.
Your test thread remains available as a record of the triage and approved reply.
Your coding agent remains able to read inbox mail while its authorization stays connected.
Your Resend API key remains a live credential while it stays active, so continue storing it securely.

Pause - I'll come back to this later

Keep the inbox and its thread for later. Disconnect the authorization that lets your coding agent read mail between sessions.

Return to the Resend connection in your coding agent from earlier.
Disconnect Resend from the agent's MCP configuration if you used MCP.
Remove the saved Resend API authorization from the coding agent if you used the API connection.
Remove the session API key from the Resend account area where you created it.
Confirm the Resend connection no longer appears among the coding agent's active connections.
Return to the Resend dashboard from earlier.
Confirm agent@your-domain.com and its existing thread remain visible.

Delete - I don't want to use this again

Remove the inbox setup when you have finished using agent@your-domain.com. Keep the inbound domain configuration if another inbox depends on it.

Return to the Resend connection in your coding agent from earlier.
Disconnect Resend from the agent's MCP configuration if you used MCP.
Remove the saved Resend API authorization from the coding agent if you used the API connection.
Remove the session API key from the Resend account area where you created it.
Return to the Resend dashboard from earlier.
Select agent@your-domain.com from the inbox list.
Use the inbox deletion option to remove agent@your-domain.com and its project thread.

The inbox list should no longer show agent@your-domain.com.

Select your-domain.com in Resend only if you configured it solely for this project.
Use the domain removal option to remove its inbound email configuration.
Confirm the coding agent no longer shows an active Resend connection.

Nice Work!

You did it. Your AI agent now has a working email address through a Resend Inbox.

You've learned how to:

Receive real messages at agent@your-domain.com as threaded conversations in Resend.
Query thread data through an API with curl. You saw the original message returned as JSON.
Run agent triage through MCP. You kept human approval in the loop before sending the drafted reply in its original thread.
Secret Mission: Complete an optional challenge that extends the agent inbox workflow.

Ready to quiz yourself?