Inventory guide

SMS routes judged on DLR, not on promises

SMS offers state the destination, the sender ID type, what kind of delivery receipt you get back, how fast you may send and what content is allowed. Those are the fields that decide whether a route works for you, so they are the fields you filter on — and the fields a dispute is judged against.

  • Sender ID type and DLR quality declared per offer
  • Throughput in SMS per second, not vague promises
  • OTP and marketing permissions listed separately
  • Prepaid balance with per-message usage logs

Sender ID types

Alphanumeric sender IDs show your brand name and are the norm for transactional traffic, but many countries require registration and will silently rewrite unregistered IDs. Numeric IDs come from long or short numbers and are more resilient. Dynamic IDs pass through whatever you send, which is powerful and heavily abused — expect restrictions.

DLR quality is the whole game

A route with fake delivery receipts reports 100% delivery while your messages vanish. Offers must state real, partial or fake DLR, and the delivery rate the seller commits to. Compare the stated delivery rate against your own results during a test batch before you scale.

  • Real DLR — receipt comes from the operator
  • Partial DLR — mixed operator and simulated receipts
  • Fake DLR — simulated, treat the delivery rate as unverifiable

Throughput and connection

Throughput is stated in SMS per second and caps how fast you can push a campaign or an OTP burst. Connection is SMPP for volume or an HTTP API for simpler integrations; binding credentials are delivered in the order page after escrow funding.

Content rules

OTP and marketing are separate permissions because operators police them separately. Routes also carry content restrictions on regulated verticals. Sending traffic a route does not permit gets the binding closed, and repeated abuse gets a buyer removed from the platform.

Prepaid and escrow

SMS orders are prepaid. Escrow funds the balance, messages draw against it, and usage logs make consumption auditable for both sides. Top up in crypto; payouts to sellers happen after escrow release, never before delivery.

What every offer must state

Country and operatorDestination network coverage
Route typeDirect, aggregator or hybrid
Sender ID typeAlphanumeric, numeric or dynamic
DLR typeReal, partial or fake
Delivery ratePercentage the seller commits to
ThroughputSMS per second accepted
OTP allowedWhether one-time-password traffic is permitted
Marketing allowedWhether promotional traffic is permitted
ConnectionSMPP bind or HTTP API
Price and billing unitPer message, with any setup fee stated

Sellers who leave a field blank still appear in results, but the offer is flagged as unconfirmed so you know what has not been verified.

Frequently asked

Keep reading