DIRECT TIER 1 CARRIER RELATIONSHIP

SMS built for AI agents.

10DLC is a pain. We make it simple. Get verified in days, send SMS and iMessage through one API, and scale without rewriting your stack. Compliance built in, not bolted on.

Request early access →
Built by the team that deployed 4,000+ agent phone numbers for a nationwide automotive platform. Early access for funded teams shipping AI agent products.
send-first-sms.sh
# Send your first SMS in 4 lines.
$ curl -X POST https://api.agentmsg.io/v1/messages/sms \
   -H "Authorization: Bearer sk_live_..." \
   -d '{
      "from": "+16165550142",
      "to":   "+14155550198",
      "text": "Hey Alex, your order shipped 📦"
   }'

{
  "id":      "msg_01HF8Z...",
  "status":  "delivered",
  "segments": 1,
  "cost":    "$0.012 + carrier"
}
a
agentmessage
PROD

Numbers

Manage phone numbers and capabilities

Active
12
Msgs today
2,481
Delivery
99.2%
All numbers 12
+1 (616) 555-0142
SMSMMS
Active
+1 (800) 555-0100
SMSMMSiM
Active
+1 (415) 555-0188
SMSMMS
Active
Direct Tier 1 carrier
Architectural compliance
SMS + iMessage, one API
Zero bulk endpoints by design

SMS shouldn't
be confusing.

Traditional CPaaS platforms were designed around bulk messaging. Agents work, but they're not what the platform was optimized for. Here's what that looks like in practice.

01

10DLC is a gauntlet of layers

Traditional CPaaS platforms were designed around bulk messaging. Their compliance flows use generic campaign categories, so your AI agent traffic gets reviewed alongside marketing blasts. That means slower approvals and more vague rejections.

Avg approval: 4–6 weeks
02

The pricing page lies

The headline rate you see is never what you actually pay. Carrier surcharges, registration fees, and volume-tier clauses are scattered across docs pages. You only learn the real cost when the first bill arrives.

You learn the real price when the bill arrives.
03

"Let's hop on a call"

Want volume pricing? Book a call. Want to use short codes? Book a call. Want MMS? Book a call. Want to actually ship your AI agent this quarter? Good luck. The sales cycle is measured in weeks.

0 self-serve for anything real
04

Dashboards from 2009

Clunky consoles, confusing error codes, webhook logs buried 5 clicks deep, no real-time anything. Your agents need programmatic everything, but most of the tooling was designed for human operators running campaigns.

Built for humans, not agents

Built for one use case.
That's the advantage.

We have the same direct Tier 1 carrier relationshipas the big platforms. The difference: we only serve AI agent traffic, so compliance is architectural rather than policy-based. No bulk endpoint. Rate limits that mirror human conversation. A two-gate consent model incumbents can't match without dismantling their own business. Our campaigns clear carrier review faster because the use case is obvious from submission.

Traditional CPaaS
You
Traditional CPaaS
Generic compliance review
Campaign Registry
Carrier
4–6 weeks
Our path
You
agentmessage (direct carrier partner)
Tier 1 carrier
4–7 days
1 hop
From your agent to the carrier.
Not four.
4–7 days
To a verified, production-ready
10DLC campaign.
0 bulk endpoints
Broadcast abuse isn't a policy we enforce.
It's architecture we built.

The SMS API
your agents deserve.

10DLC registration, carrier negotiations, consent tracking, opt-out detection. All of it, out of the box. You ship messages, we ship compliance.

01 / SPEED

Verified in a week

Our architectural compliance model (two-gate consent, no batch sends, automatic opt-out) means cleaner campaign submissions. 10DLC goes straight from us to the carrier. Submit once, launch in days.

Average: 4.2 days
02 / PRICING

Priced for scale

Three tiers that scale with your deployment, from $49/month Starter through $1,499/month Scale. Per-segment pricing with every carrier fee passed through at cost, shown on one page, not buried across docs. No volume-tier surprises. No sales call to see the number.

All costs on one page
03 / UNIFIED API

One API, SMS and iMessage

Unified endpoint sends SMS, MMS, or iMessage from the same number pool. iMessage add-on from $130/line/month with no per-message cost and instant provisioning. Automatic iMessage detection with SMS fallback for non-Apple recipients. Idempotent calls, signed webhooks, automatic opt-out detection, and a consent table your agents can query before every send. Compliance is the default, not a library you import.

HMAC webhooks · Consent API

One endpoint. Every carrier.

cURL
Node.js
Python
Go
POST /v1/messages/sms
# Provision a number and send an SMS. One agent, one script.
$ curl -X POST https://api.agentmsg.io/v1/numbers/provision \
   -H "Authorization: Bearer sk_live_..." \
   -d '{ "number_type": "local", "preferences": { "area_code": "616" } }'

< "number": "+16165550142", "status": "active">

$ curl -X POST https://api.agentmsg.io/v1/messages/sms \
   -d '{ "from": "+16165550142", "to": "+14155550198", "text": "hi" }'

delivered · $0.012 + carrier · msg_01HF8Z7Q9X...

Your users' PII is never ours.
By design, not policy.

We are not a data broker pretending to be an API. Phone numbers are encrypted at rest with per-tenant keys, message content is never mined, and we hold zero personally identifiable information about your end users beyond what the carrier absolutely requires to deliver a text. Your contact lists stay in your system. We route bytes, we don't hoard people.

01 / ENCRYPTION

Phone numbers encrypted at rest

Every destination number is encrypted with AES-256 using per-tenant keys managed in an HSM-backed KMS. Plaintext numbers never touch disk, never appear in logs, and never leave the send path. TLS 1.3 on every hop in and out.

AES-256 · per-tenant keys
02 / ZERO PII

We do not store your users' PII

No names, no emails, no addresses, no CRM profiles. Your contact graph lives in your system. We hold the minimum routing metadata a carrier needs to deliver a segment, and nothing we store can be joined to an identity without data you already own.

Minimum viable metadata
03 / ISOLATION

Tenant isolation all the way down

Row-level tenancy, signed webhooks with replay protection, short-lived API keys scoped per number pool, and full audit trails on every consent and send. Your data is cryptographically walled off from every other tenant on the platform.

HMAC webhooks · scoped keys
0 PII
Stored on end users beyond
carrier-required routing data.
AES-256
Per-tenant encryption on every
phone number at rest.
TLS 1.3
On every request, webhook, and
carrier hop. No exceptions.

agentmessage vs. Traditional CPaaS

a agentmessage
Traditional CPaaS
10DLC verification
4–7 days, handled for you
Weeks, mixed in with all traffic types
Setup / registration fees
$0, included
$50–$4,000 to get started
Pricing transparency
Calculator + carrier table on one page
Base rate on one page, carrier fees on another, volume clauses in a third
Bulk endpoint
None, structurally impossible to misuse
Available, your liability
iMessage via same API
From $130/line/mo add-on, unified endpoint, auto-fallback
Separate product or not supported
Sales call required
Custom tier only
For nearly everything
Consent & opt-out detection
Automatic & queryable
You build it yourself
Built for AI agents
From day one
Optimized for bulk messaging
Time to first SMS
< 60 seconds (sandbox)
Weeks, after approvals

No quotes. No sales calls.

Three tiers that scale with your deployment. Per-segment pricing with every carrier fee passed through at cost.

Starter

For first agent products

$49/ month
$0.015/message segment + carrier fees at cost
  • Up to 10 phone numbers
  • 10DLC registration included
  • Full compliance suite with campaign review
  • Webhook retry, DLQ, dedicated number pool
Request early access →
Scale

Production agent fleets

$1,499/ month
$0.010/message segment + carrier fees at cost
  • Up to 500 phone numbers
  • Custom rate limits tuned to your use case
  • Advanced usage analytics
  • Named support, 4-hour response
Request early access →

Full pricing breakdown, calculator, and carrier fee table →

Questions we get a lot.

Quick answers for developers building AI agents that need to send and receive text messages.

What is agentmessage?+
agentmessage is an SMS API built specifically for AI agents. It provides phone numbers, messaging, and compliance infrastructure so developers can have their AI agents send and receive text messages at scale. agentmessage is a direct Tier 1 carrier partner focused exclusively on AI-to-person messaging.
How is agentmessage different from Twilio or Sinch?+
Twilio and Sinch are built for bulk messaging: marketing campaigns, promotional blasts, high-volume transactional SMS. That’s where their revenue comes from, and their compliance architecture has to accommodate it. agentmessage is built for the opposite. We have no bulk endpoint. Our rate limits mirror human conversation. Our consent model gates every outbound message against a relationship-aware contact graph. These are design choices the incumbents can’t copy without dismantling their core revenue. For teams shipping AI agents: 10DLC verification takes days instead of weeks, campaigns stay verified as you scale, and the compliance work you’d otherwise own is handled architecturally. SMS and iMessage share one unified API. Send through either, with automatic fallback to SMS when the recipient isn’t on Apple.
How much does agentmessage cost?+
Three tiers: Starter at $49/month for up to 10 numbers, Growth at $299/month for up to 100 numbers, and Scale at $1,499/month for up to 500 numbers. Per-message-segment rates range from $0.010 to $0.015 depending on tier, with carrier fees passed through at cost (typically $0.002–$0.004/message segment). iMessage for Business is available on every tier as an add-on with no per-message cost, at $150/line/month on Starter, $140/line/month on Growth, and $130/line/month on Scale. Custom pricing for teams sending 1M+ segments/month. Full breakdown and interactive calculator on the pricing page.
How fast can I start sending SMS with agentmessage?+
Sandbox sending is instant. Production 10DLC verification averages 4 to 7 days because agentmessage handles brand and campaign registration directly with the carrier, and our architectural compliance model (two-gate consent, no batch sends) means cleaner submissions.
Does agentmessage support iMessage for Business?+
Yes. iMessage for Business is available on every tier as an add-on with no per-message cost and instant provisioning. Pricing: $150/line/month on Starter, $140/line/month on Growth, $130/line/month on Scale, and negotiated on Custom. Use the same unified API to send SMS, MMS, or iMessage from the same number. Apple Business Register verification is handled as part of onboarding, with automatic SMS fallback for recipients who don’t have Apple devices.
Is agentmessage compliant with TCPA and carrier regulations?+
Yes, and compliance is enforced architecturally rather than as policy. Every outbound message passes through a two-gate check: either the contact must have texted the number first, or explicit consent must have been logged through the consent API. Opt-outs (STOP, UNSUBSCRIBE, etc.) are detected automatically. There is no batch send endpoint by design, so volume spam is structurally impossible.
What’s AI2P?+
A term we use internally (and starting to use publicly) to distinguish what we do from A2P. A2P is application-to-person: bulk SMS, marketing campaigns, the category every major provider optimizes for. AI2P is AI-to-person: stateful, bidirectional conversations between AI agents and real users. Different traffic shape, different compliance profile, different product. We built for AI2P from day one.

Request early access.

Rolling out to funded teams shipping AI agent products. Tell us what you're building and we'll reach out when your spot is ready, typically within a week.

One or two sentences. Helps us prioritize your spot.

We read every submission. Funded teams and teams with specific agent use cases get prioritized.