Per-Message Billing for Email, SMS, and Voice APIs
Bill for every email sent, every SMS delivered, and every voice call made. Wrap Twilio, Resend, SendGrid, or any communication API with per-message metering.
How it works
import { settlegrid } from '@settlegrid/mcp'
import { Resend } from 'resend'
const sg = settlegrid.init({
toolSlug: 'my-email-service',
pricing: {
methods: {
'send_email': { costCents: 1 },
'send_sms': { costCents: 3 },
},
},
})
const resend = new Resend(process.env.RESEND_API_KEY)
const billedEmail = sg.wrap(async (args: { to: string; subject: string; body: string }) => {
const result = await resend.emails.send({
from: 'notifications@myapp.com',
to: args.to,
subject: args.subject,
html: args.body,
})
return { content: [{ type: 'text', text: `Email sent: ${result.id}` }] }
}, { method: 'send_email' })Supported providers
SettleGrid works with any provider. Here are the most common ones for communication apis.
| Provider | Pricing |
|---|---|
| Twilio | SMS, voice, WhatsApp -- per-message pricing |
| SendGrid | Email delivery -- per-email pricing |
| Resend | Developer email API -- per-email pricing |
| AWS SES | Bulk email -- $0.10/1000 emails |
| MessageBird | Omnichannel messaging -- per-message pricing |
Why per-message billing?
Communication APIs have the cleanest billing model: per-message. Every email sent, every SMS delivered, every voice minute consumed maps to a single billable event. SettleGrid meters each message type at its configured rate and settles in real time. Method-level pricing lets you charge different rates for email, SMS, and voice.
$17.2B
Total Addressable Market
5
Supported Providers
2 min
Setup Time
Frequently asked questions
Can I charge differently for email vs SMS vs voice?
How do I handle voice call billing (per-minute)?
What about bulk sending discounts?
Do agents need to authenticate to send messages?
Start billing communication apis today
Add per-message billing to your communication apis service in under 2 minutes. No upfront costs, no contracts.