Email infrastructure your coding agent can actually operate.

Give a trusted agent a clear project and permission grant. It can create, verify, send, inspect, and maintain the email path through the same API your app uses.

Get your API key Read the agent quickstart

Explicit authority

A key is not a blank check.

NoticeAPI checks the capability, project, and sender domain on every request. Platform safety rules apply after authorization.

API keyntc_••••••••

Projectacme-store only

Senderacme.store only

Safety checksquota · consent · suppression

Use the interface that fits the job

MCP for the agent. REST for the app. One grant model.

Connect a hosted MCP client, run the local stdio package, or call the management API directly. Project and capability boundaries stay consistent.

MCP guide API reference

Hosted MCPTool discovery and structured results

/mcp

Local stdioUse NOTICEAPI_API_KEY

npx noticeapi-mcp

Management APIProjects, domains, templates, logs, and more

/api/v1

Review the work, not a success sentence

Every action leaves product evidence.

Simulator outcomeDelivered, bounced, complained, or suppressed Recipient timelineRequest, provider, and webhook events DNS statusInstalled, public, and provider-verified

Before you connect an agent

Keep the boundary visible.

Does a coding agent need full workspace access?

No. Use full access for a trusted operator, sending-only access for an app, or a custom key limited to selected projects, domains, and capabilities.

Can an agent bypass unsubscribe or suppression rules?

No. API authority controls which operations a key may request. Consent, unsubscribe, suppression, quota, abuse, and sender checks still apply.

Let the agent finish the email integration.

Choose the project and capabilities, verify the domain, and send the first customer receipt.

Get your API key Agent quickstart