TextKit

About TextKit

TextKit is an SMS API built for developers who need to send and receive texts in the US and Canada. It handles 10DLC brand and campaign registration, automatic STOP/START/HELP keyword processing, and integrates with over 100 services including Claude and ChatGPT through an MCP server. The tool launched this week and comes from a maker who built it after finding existing SMS integration unnecessarily complicated for his own applications.

Review

Adding SMS to an application involves more than just sending a message - carrier registration, compliance, and error handling can stretch a weekend project into weeks of paperwork. TextKit enters the market as a developer-focused API that automates much of that overhead. It's positioned as a lower-cost alternative to established providers, with a stated price of $0.002 per text plus carrier fees at cost.

Key Features

• Full API test environment that doesn't send real texts during development
• Automated 10DLC brand and campaign registration filing
• Built-in handling of STOP, START, and HELP keywords for compliance
• MCP server integration enabling use with Claude, ChatGPT, and Cursor
• Two-way texting with signed webhooks, SDKs, and a CLI available from launch

Pricing and Value

TextKit offers a free tier starting at $0 per month. Outbound texts cost $0.002 each, plus the underlying carrier fee passed through at cost. The maker states this is roughly 50% cheaper than Twilio's per-message pricing. At this early stage, detailed pricing tiers beyond the free plan haven't been published, and the long-term pricing model isn't yet defined.

Pros

• Per-message cost is lower than major competitors, with carrier fees passed through without markup
• 10DLC registration is handled by TextKit rather than requiring the developer to navigate it alone
• Message failure and filtering details are surfaced so developers can see what went wrong
• Human support is available when problems arise, rather than automated-only channels
• SDKs, CLI, and webhook signing were included from day one rather than added later

Cons

• The service only supports US and Canada phone numbers, which rules out international messaging use cases
• As a week-old launch, the API has no production track record or long-term reliability data to evaluate
• TextKit is not well suited for teams that need advanced messaging features like WhatsApp, video, or omnichannel routing - it's strictly SMS

TextKit fits developers and small teams who need straightforward SMS for 2FA codes, notifications, or marketing messages within North America and don't want to manage carrier registration themselves. The free tier and lower per-text cost may appeal to those watching their messaging budget, though teams with complex multi-channel needs or international audiences will find the scope too narrow. As with any newly launched API, early adopters should test thoroughly before committing production workloads.