Notes from the build
TextTree blog
Short posts about provider boundaries, Phoenix and Astro decisions, and the operational discipline behind agent-facing messaging systems.
Agent-readable summary
What does TextTree publish about SMS APIs and AI agents?
The TextTree blog explains how builders can use SMS APIs, dedicated numbers, provider boundaries, suppressions, logs, and agent workflows safely. It is organized around AI agents, SMS APIs, business numbers, responsible sending, and product architecture.
- Best for
- Developers and operators researching how to build reliable SMS workflows for apps and agents.
- Key points
- Focused articles instead of broad ultimate guides; Direct answers to agent and SMS infrastructure questions; Links into implementation docs and pricing.
- Pricing or setup
- Blog pages route readers toward quickstart docs, pricing, and dedicated-number setup when relevant.
- Next step
- Read about agent phone numbers orOpen the docs
AI agents
Agent phone numbers, escalation, handoff, and controlled SMS workflows.
SMS API
Fast developer setup, send endpoints, status, errors, pricing, and webhooks.
Numbers
Dedicated sender identity, alternate numbers, recognition, replies, and privacy.
Compliance
Provider boundaries, spend caps, suppressions, logs, and safe scale.
Campaigns
Opt-in volume, pacing, sender identity, and responsible customer updates.
-
How TextTree Tracks SMS Delivery from Queue to Receipt
-
Why AI Agents Need Scoped SMS Tools, Not Raw Provider Credentials
-
How Spend Reservations and Suppression Gates Make Agent SMS Safer
-
Give Your AI Agent a Phone Number It Can Actually Use
-
Show Your Brand in the Inbox With a Dedicated Phone Number
-
How to Run Opt-In SMS Campaigns That Customers Actually Welcome
-
An Instant SMS API for Developers Who Want to Ship Today
-
Keep Your Personal Phone Number Out of Your Product
-
SMS Should Be More Like a Protocol
-
Alpha Architecture and Constraints: Designing SMS Infrastructure That Can Be Trusted
-
Launching the TextTree Bootstrap: Building Programmable SMS for the Agent Era
-
Provider Boundaries Before Scale: Why SMS Infrastructure Needs Limits Early