SMS API for AI agents and apps

Instant SMS for AI agents & Apps.

Communication should be programmable. Textree lets apps and agents get a number, send a message, receive replies, and inspect delivery from one operator-ready API.

AI agents Apps Reminders Support Lead follow-up
POST /api/v1/messages Test mode
curl https://api.texttree.ai/api/v1/messages \
  -H "Authorization: Bearer $TEXTREE_KEY" \
  -d "phone_number=+15551234567" \
  -d "body=Your appointment is confirmed."
  1. 10:01:04 API request received
  2. 10:01:05 Message queued
  3. 10:01:06 Sent to carrier
  4. 10:01:12 Delivered
  5. 10:01:13 Webhook delivered

How it works

1

Get a number

Rent or connect a sender and keep test mode clearly separated from live traffic.

2

Send SMS via API

Use one endpoint for reminders, agent messages, alerts, and customer conversations.

3

Receive replies

Route inbound SMS through webhooks, conversations, contacts, and handoff states.

4

Monitor delivery

Debug failures with timelines, event logs, cost data, and webhook replay.

Why Textree exists

SMS should feel more like a protocol.

Developers should not have to stitch together number inventory, delivery logs, webhook replay, spend controls, and operator handoff just to send one reliable message. Textree gives AI agents, apps, and operators a clean path: start fast, then graduate into branded numbers and high-volume workflows when the use case proves itself.

Product modules

Everything around the first successful SMS.

Outbound API

Send transactional, reminder, support, and agent messages through one developer-friendly endpoint.

Inbound SMS

Route replies into conversations, webhook events, and human handoff workflows.

Webhook debugging

Inspect payloads, delivery attempts, response codes, latency, and replay status.

Message logs

Search status, cost, provider identifiers, failures, and full message timelines.

AI handoff

Pause automation, assign conversations, add notes, and resume agents when ready.

Compliance tools

Track opt-in, opt-out, registration readiness, billing, and live-mode gates.

Developer section

Copy-pasteable examples and inspectable events.

Start with curl, then move to JavaScript, Python, or Elixir. Every send, webhook, and failure is traceable from the dashboard.

Open the quickstart →
{
  "id": "msg_123",
  "status": "queued",
  "segments": 1,
  "cost": "$0.01",
  "next": "Watch delivery status in message logs"
}

Use cases

Built for product teams and operators.

Comparison

Simpler than legacy SMS APIs, with logs and agent-ready webhooks by default.

Compare Twilio →

Pricing preview

Start fast, then graduate into branded numbers.

Starter

$20/mo

400 messages/month for the first real Fast Send workflow.

Growth

$100/mo

2,000 messages/month for customer workflows and basic campaigns.

Scale

$500/mo

10,000 messages/month, branded numbers, and operational support.
See pricing →