REST API · MCP Server · TypeScript SDK

Text messaging inboxes
for AI agents

Give your agents real phone numbers. Create inboxes, send and receive texts, parse OTPs, thread conversations — all via API.

Free to start · $5 credit included · no credit card

MSG LOG

inb_7x9k2m · +1 (415) 555-0142

active
AGENTPlease verify your account to continue.
CONTACTYour verification code is 847291. Do not share this code.
PARSEDotp_code: 847291· category: otp
AGENTVerification complete. Logging you in now.
STATUS✓ flow completed in 2.3s

Why AgentText?

Built for agents, not humans

Most SMS tools were built for support teams. AgentText is built for agents that need persistent identity, OTP handling, and real-time message access.

agenttext★ recommended
  • Purpose-built for agents
  • OTP auto-parsing
  • First-class MCP server
  • Conversation threading
  • HMAC webhooks + retries
  • A2P compliance handled
  • 3 lines to start

twilio

  • General telecom API
  • OTP parsing — your regex
  • No MCP support
  • No threading — you build it
  • Webhooks — you configure
  • A2P — DIY registration
  • ~200 lines to start

build it yourself

  • You own the infra
  • You write the parser
  • You write MCP adapters
  • You build threading
  • You build retry logic
  • You handle compliance
  • Months to start

Features

Everything in one API

Persistent phone numbers

Each inbox = one real US phone number. Yours as long as you need it. Not a temporary session that vanishes.

inb_7x9k2m

+1 (415) 555-0142

activeagt_mK92x340ms

OTP auto-parsing

Verification codes extracted from inbound texts automatically. Your agent reads the code. You don't write the regex.

inbound message

“Your verification code is 847291. Do not share.”

parsed →

847291otp

Native MCP support

First-class Model Context Protocol. Works with Claude, Cursor, and any MCP-compatible agent framework.

mcp.json
{
  "mcpServers": {
    "agenttext": {
      "command": "npx"
      "args": ["agenttext-mcp"]
    }
  }
}

Real-time webhooks

HMAC-signed callbacks when texts arrive. Built-in retry logic. Svix-compatible headers.

POST/your-webhook
200 OK
{
  "type": "message.received",
  "inbox_id": "inb_7x9k2m",
  "body": "Your code is 847291",
  "otp_code": "847291",
  "category": "otp"
}

Use Cases

Built for real work

qa-automation/

QA Automation

Agents that verify SMS-gated flows end-to-end — signup, OTP, 2FA — without a human holding a phone.

account-verify/

Account Verification

Autonomous onboarding agents that receive OTPs, parse codes, and complete verification in one shot.

agent-comms/

Agent Communication

Give your AI workers real phone identities. Send and receive texts as part of multi-step autonomous workflows.

dev-testing/

Dev & Testing

Provision throwaway numbers per test run. Isolate inboxes, assert on messages, clean up on teardown.

Integration

Ways to integrate

TypeScript SDK, Python SDK, REST API, or MCP server. Works with Claude Code, Cursor, Windsurf, and any MCP client.

import { AgentText } from "agenttext";

const client = new AgentText("at_live_...");

// provision a phone number
const inbox = await client.inboxes.create({
  display_name: "OTP Verifier",
  area_code: "415"
});

// send a text
await client.messages.send(inbox.id, {
  to: "+15551234567",
  body: "Verify my account"
});

// wait for the OTP reply
const reply = await client.messages.waitFor(inbox.id);
console.log(reply.otp_code); // → "847291"

Pricing

Start free. Scale when ready.

$5 credit included on every account.

free

$0/mo

+ $5 free credit

  • 1 inbox (phone number)
  • ~100 texts from credit
  • $0.05/text after credit
  • OTP parsing
  • MCP server access
  • 30-day retention
Get started

builder ★

$29/mo

2,000 texts included

  • 5 inboxes (phone numbers)
  • 2,000 texts/mo included
  • $0.03/text overage
  • Full message parsing
  • 5 webhook endpoints
  • 90-day retention
Get started

scale

$149/mo

15,000 texts included

  • 25 inboxes (phone numbers)
  • 15,000 texts/mo included
  • $0.025/text overage
  • Custom parsing rules
  • 15 webhook endpoints
  • 1-year retention
Get started

FAQ

Questions

What phone numbers are available?+
US numbers provisioned instantly via API. Area code selection supported. More regions coming — contact us if you need international coverage.
How does OTP parsing work?+
Inbound messages are scanned for verification code patterns automatically. The parsed code comes back as otp_code on the message object — no regex required on your end.
How is this different from Twilio?+
Twilio is a general-purpose telecom API. AgentText is purpose-built for agents: conversation threading, OTP parsing, MCP support, and HMAC-signed webhooks are all first-class. What takes 200 lines with Twilio takes 3 with AgentText.
What does MCP support mean?+
AgentText ships as an MCP server. Claude Code, Cursor, Windsurf, or any MCP-compatible agent can create inboxes, send texts, and receive messages through native tool use.
Is A2P compliance handled?+
Yes. We handle carrier registration and A2P 10DLC compliance on your behalf. You send texts; we manage the regulatory overhead.

Your agent deserves
a phone number.

Sign up free. $5 credit included. No credit card required.

$
·SMS FOR AGENTS·REST + MCP + SDK·AGENTTEXT.DEV·OTP PARSING·REAL PHONE NUMBERS·BUILT BY SHOPERATORS·CONVERSATION THREADING·HMAC WEBHOOKS·CURSOR NATIVE·CLAUDE NATIVE·SMS FOR AGENTS·REST + MCP + SDK·AGENTTEXT.DEV·OTP PARSING·REAL PHONE NUMBERS·BUILT BY SHOPERATORS·CONVERSATION THREADING·HMAC WEBHOOKS·CURSOR NATIVE·CLAUDE NATIVE