💸ratemypricing★ github
← leaderboard
📄 markdown🕑 19h ago🛠️ DevTools

Telnyx

telnyx.com ↗

Single messaging API priced entirely by usage with base rates plus carrier-specific passthroughs and piecewise volume discounts per sender/media/direction. While usage-based billing is common in devtools, the many carrier- and channel-specific meters and a custom contract tier make exact costs scenario-dependent.

model: gpt-5
0🧾
Pricing clarity
Pretty tangled
0🤖
Agent easiness
Rough for bots
📐 how these scores work

How we scored it 🧮

Every page starts at 100. Each kind of complexity subtracts points — here's the math.

🧾 Pricing clarity

41
  • Base score+100
  • 14 in-plan configuration choices-16
  • 184 metered dimensions to track-26
  • Pure usage pricing — no flat plan to anchor the bill-17
  • Total41 / 100

🤖 Agent easiness

40
  • Base score+100
  • No concrete pricing to parse-40
  • Real pricing isn't on the pricing page (scattered across pages)-20
  • Total40 / 100

The pricing tree 🌳

tap any branch to explore
💳 Usage-based💱 $🪜 2 tiers

The tiers 🪜

Pay as you go
Pay-as-you-go
  • ✦Pay only for messages sent/received
  • ✦Pricing per message part varies by sender type (Local/10DLC, Toll-Free, Short Code, RCS) and carrier fees may apply
  • ✦Automatic volume discounts after threshold (varies by sender type)
Volume-based pricing
Custom
  • ✦Contract with predictable monthly payments
  • ✦Discounted rates versus pay-as-you-go based on monthly commitment
  • ✦Free 24/7 support and dedicated customer success manager

Watch out for 🕵️

  • ⚠️No inclusive allowance; all pricing is per-message/segment usage
  • ⚠️Multiple parallel metered dimensions to sum: base message rates plus carrier-specific passthrough fees
  • ⚠️Rates vary by sender type (Local/10DLC, Toll-Free, Short Code, RCS) and by direction (inbound/outbound) and media type (SMS/MMS/RCS)
  • ⚠️Carrier fees differ by individual carrier and can be zero or non-zero, requiring carrier mix assumptions
  • ⚠️Volume discounts are piecewise with large thresholds and separate ladders per traffic type, complicating forecasting
  • ⚠️Custom volume-based plan requires sales contact with undisclosed rates