What would you want from a "Resend for SMS" dev tool?
Hey everyone, I'm Daniel, building Relay. We're launching here soon and wanted to start a conversation first.
The short version: I kept spending entire days integrating SMS into projects that only needed to send a verification code. Twilio has 47 endpoints. AWS SNS needs IAM policies and origination identity setup. Every time, a 5-minute feature became a 5-hour detour.
So I built an SMS API where you sign up, get a key, and send your first text in under 2 minutes. One endpoint. Five lines of code.
Two things I'm especially curious to get feedback on:
1. Agent-native SMS. AI agents can create their own accounts and start sending via API — no human setup required. We built this because we kept seeing agent frameworks that needed SMS as an output channel but had no clean way to provision it. Is this something you'd actually use, or is it too early?
2. Local testing with sms-dev. We open-sourced a local dev tool (think Mailtrap for SMS) so you can test your entire flow without sending real messages. It's free and standalone — works even if you never use Relay in production. Curious if anyone's wanted something like this.
Right now we cover US and Canada. Pricing starts at $19/month with 1,500 messages included.
What would matter most to you in an SMS API? Speed of integration? Price? Deliverability? International coverage? Would love to hear what's shaped your experience with SMS so far.



Replies