What your agent can do
- Send an email, safely retried with the same
idempotency_key. - List sent emails and read the delivery status of each.
- Add a sending domain, give you its DNS records, then verify it.
- Create and publish email templates, and manage suppressed addresses.
Ask your agent
Paste a request like these in your AI once it is connected. It calls the tools in this order.
| You ask | Your agent calls |
|---|---|
| “Send a welcome email to ana@example.com from hello@acme.com.” | get_status → send_email → get_email |
| “Set up mail.acme.com to send email.” | list_domains → add_domain → get_domain → verify_domain |
| “Did any of my last emails bounce?” | list_emails → get_email |
| “Create a welcome template and publish it.” | create_template → publish_template |
Tools and routes
Every tool is a call to the REST route next to it, with the same permissions, limits and idempotency. tools/list shows only the tools your connection can call.
| Tool | What it does | Scope | Same through the REST API |
|---|---|---|---|
get_status | Project, environment, sending mode and the services open to this key. | none | GET /v1/tools |
send_email | Send one email. | mail:send | POST /v1/emails |
list_emails | List sent emails, newest first. | mail:send, job:read | GET /v1/emails |
get_email | Read one sent email and its status. | mail:send, job:read | GET /v1/emails/{email_id} |
list_domains | List sending domains and their status. | full_access | GET /v1/domains |
add_domain | Add a sending domain. | full_access | POST /v1/domains |
get_domain | Read a sending domain and its DNS records. | full_access | GET /v1/domains/{domain_id} |
verify_domain | Check a domain's DNS records now. | full_access | POST /v1/domains/{domain_id}/verify |
list_templates | List email templates. | template:read | GET /v1/templates |
create_template | Create a template draft. | template:write | POST /v1/templates |
publish_template | Publish a template so send_email can use it. | template:write | POST /v1/templates/{template}/publish |
list_suppressions | List addresses that will not receive email. | full_access | GET /v1/suppressions |
add_suppression | Stop all email to these addresses. | full_access | POST /v1/suppressions |
Limits, free tier and pricing
Read from the platform code each time this page is served.
| Limit | Value |
|---|---|
| Recipients per email (to, cc and bcc together) | 50 |
| Attachments per email | 10 |
| Email size after encoding, attachments included | 25 MB |
| Emails per batch request | 100 |
| Scheduling horizon (scheduled_at) | 3 days |
| Text or HTML body, each | 48 KiB |
| Message size after encoding, attachments included | 25 MB |
Free plan (no card): 3,000 transactional emails a month, 100 a day. Hard limits: a send beyond them is refused, never billed.
Paid plans, per month, in US dollars. The plan's monthly volume is a hard limit: there is no overage billing.
| Plan | Price per month | Emails per month |
|---|---|---|
starter | 5.39 USD | 10,000 |
pro_50k | 15.00 USD | 50,000 |
pro_100k | 27.00 USD | 100,000 |
scale_250k | 62.00 USD | 250,000 |
scale_500k | 115.00 USD | 500,000 |
scale_1m | 210.00 USD | 1,000,000 |
scale_2_5m | 475.00 USD | 2,500,000 |
Your agent reads the current prices with get_pricing and the spending limits with get_limits.
Good to know
- Nothing is sent from an unverified domain: the DNS records are published at your DNS host, then verified.
- Domains and suppressions need a connection with
full_access; sending needsmail:send.