AgentMail or a send-only provider — no shared conversation with SMS
email + SMS + hosted MCP — one identity
Your agent needs
a real identity.
One identity owns an inbox, a real US number, and a hosted MCP URL. One thread. Communications built so an agent can show up, not so a human can click around.
No credit card for the first identity. SMS is sent only after the recipient opts in at r3y.dev/sms. SMS
# one identity — not an SDK create() MCP https://r3y.dev/mcp/{identity} email {name}@r3ymail.com sms +1 … bound to the same identity — issued after setup and used only with opted-in people
The problem
You built the agent.
Then you bought an inbox product and a number product and still did not have one conversation.
Separate APIs, separate webhooks, no shared thread. r3y is one identity layer — inbox, number, and connector — without claiming voice or outbound SMS.
The fragmented approach
A different provider, a different webhook, a different identity
You still do not have one conversation the agent can read
r3y — one layer
Inbox plus a US local number on the same object
Email and inbound SMS land on the same conversation
OAuth + bearer at https://r3y.dev/mcp/{identity}
Features
Everything a communicating agent needs.
Nothing it doesn't — and nothing we cannot ship yet.
Hosted MCP at the identity URL
OAuth and an identity-scoped bearer. The path is the bind — not an account picker.
Full inbox
Send and receive, threading, CC/BCC, and attachments on {name}@r3ymail.com. You can bring a domain.
US local number + inbound SMS
A real US number on that identity. Inbound SMS joins the same thread as email. SMS is sent only after the recipient opts in at r3y.dev/sms. SMS
Email login
We email a code from r3ymail.com. Same origin as this page.
Request log
What the agent did — action, caller, result. Tokens and message bodies are not stored.
Voice — coming soon
Voice is coming soon.
What you do not get yet
- Outbound SMS — coming soon.
- Voice — coming soon.
The API
The identity is the
primitive.
Not the phone number. Not the inbox. One object owns everything. There is no public SDK create() — paste the identity URL.
# one identity — not an SDK create() MCP https://r3y.dev/mcp/{identity} email {name}@r3ymail.com sms +1 … bound to the same identity — issued after setup and used only with opted-in people
The agent is the primitive
Inbox, number, and hosted MCP URL belong to one identity.
One thread for email and inbound SMS
Same peer, same conversation_id.
One event surface — the request log
See what the agent called. Prefix only is logged for bearers.
MCP — Model Context Protocol
The identity URL is the
connector.
Paste the hosted identity MCP URL into a client. We do not ship npx, npm, or pip. Auth is OAuth or a bearer you mint after sign-in.
- ✓
agents_get— Bound identity (self). The URL path is the identity — no id argument. - ✓
numbers_buy— Buy a US local number if this identity is still on a stub. First live buy is one number. - ✓
messages_send— Send or record a message as the bound identity. Email is live (threading, CC/BCC, attachments). Outbound SMS is not. - ✓
threads_list— List conversation threads for the bound identity. - ✓
requests_list— List recent MCP and identity API calls for the bound identity. - ✓
billing_get— Read this account's billing_status (none / active / past_due). Read-only. Does not charge a card.
{
"mcpServers": {
"r3y": {
"url": "https://r3y.dev/mcp/{identity}"
}
}
}
Pricing
Start free.
Scale as your agents do.
First identity is free. Extra identity is $8/month. Number is billed separately — not in the identity price. Email and SMS stay usage.
Free
$0 / month
One identity, usage on email and inbound SMS. No credit card needed to start.
- ✓ 1 identity
- ✓ Email inbox
- ✓ Inbound SMS
- ✓ Hosted MCP
- ✓ BYOK
- – Extra identity seats
Paid
$8 / month
Per extra identity. First identity is free. Number, when attached, is billed separately.
- ✓ Extra identity seats
- ✓ Email + inbound SMS usage
- ✓ Hosted MCP
- ✓ Number is billed separately
Enterprise
Talk to us
Volume and invoicing for platform teams. We do not list compliance programs as done.
- ✓ Talk to us about volume and terms
- ✓ Same live product: email, inbound SMS, hosted MCP
Questions
What is live, docs, and numbers — as they are, not as a launch deck.
Where are the docs?
A real /docs page — MCP identity URL and the identity model. There is no public SDK.
Do you port numbers?
We bind a US local to the existing identity. We do not advertise free porting.
Get started
One identity.
Inbox, number, hosted MCP.
No credit card for the first identity.