I built a Telegram bot that exposes real SMS routing

I wanted a Telegram bot that did more than trigger a fixed SMS request. Most SMS APIs hide routing. You send a message → it gets delivered (or not) → and you don’t know: which route was used why delivery changes how pricing is applied So I built a Telegram bot directly on top of BridgeXAPI that exposes everything: /balance /routes /pricing /send <route_id> <number> <message> No abstraction. No hidden routing. You choose the route yourself. Example: /send 3 31651860670 Your verification code is 4839 That maps directly to: client . send_sms ( route_id = 3 , caller_id = " BRIDGEXAPI " , numbers = [ " 31651860670 " ], message = " Your verification code is 4839 " ) The idea is simple: If routing matters, it should be visible. If pricing depends on routes, it should be queryable. If you're building systems, not dashboards — you need control. GitHub: https://github.com/bridgexapi-dev/bridgexapi-telegram-bot Docs: https://docs.bridgexapi.io