Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
Numscope
Free Carrier Lookup API for developers
9 followers
Free Carrier Lookup API for developers
9 followers
Numscope is a simple, fast, and free Carrier Lookup API built for developers, telecom companies, SMS platforms, VoIP providers, and verification services. Instantly determine the carrier behind a phone number using a clean REST API, secure API keys, generous rate limits. Instant carrier detection, country, number type, formatting, timezones and batch lookups. Sub-second, developer-first phone number intelligence API.
Tested a few numbers and the response time was impressively snappy, plus the batch lookup endpoint saved me from scripting a loop. The free tier with proper API keys is a nice touch for a quick side project.
@lhanmarangfclk Thank you so much! I'm really glad to hear that. Keeping the API fast and easy to integrate was one of my biggest goals from the start. I'm especially happy the batch lookup endpoint saved you some development time, that's exactly the kind of workflow improvement I hoped it would provide. I also wanted the free tier to be practical so developers can build and test real projects. Thanks for trying Numscope, and I'd love to hear any suggestions you have as you continue using it! 🚀
Loving the simplicity here, exactly what I needed for cleaning up my SMS routing logic. One thing that would be a huge win for me is a webhook option for batch lookups so I don't have to keep polling large jobs, just fire it off and get pinged when it's done.
@hatunkeski92266 Thank you! I'm really glad Numscope is helping with your SMS routing workflow. That's exactly the kind of use case I had in mind when building it. 😊
I also appreciate the webhook suggestion, that's a great idea. While the current batch endpoint is optimized for fast processing, webhook-based asynchronous jobs would be a great addition for larger workloads and would eliminate the need for polling. It's definitely something I'll consider as I expand the API. Thanks for taking the time to share such valuable feedback, and please keep the ideas coming! 🚀
Sub-second lookups actually feel instant, and the batch endpoint saved me a ton of time on a verification project. Clean docs and the free tier is generous enough to actually test things properly.
@ekutbe72210 Thank you so much! I'm really glad to hear the performance and batch endpoint made a difference for your workflow. Speed and a straightforward developer experience were two of my biggest priorities when building Numscope, so it's great to know they're delivering value. I also wanted the free tier to be generous enough that developers could properly evaluate the API before committing. Thanks again for trying it out, and if there's anything you'd like to see added or improved, I'd love to hear your feedback! 🚀
Clean docs and the response time is genuinely fast, batch endpoint worked first try.
@hiradeveci Thank you! I'm really happy to hear that. I spent a lot of time making the documentation as straightforward as possible because I wanted developers to be able to integrate Numscope without unnecessary friction. It's also great to know the batch endpoint worked seamlessly for you, that was one of the features I wanted to get right from day one. I really appreciate you giving Numscope a try, and I'd love to hear any ideas you have for improving it further. 🚀
finally a carrier lookup that doesn't feel like a clunky enterprise tool. tried it with a few numbers and the response time is genuinely snappy, plus the batch endpoint saved me a ton of requests.
@kazmmrselrgym Thank you so much! That was exactly the experience I wanted to create. Many existing carrier lookup APIs are powerful, but they can also feel overly complex for developers who just need fast, reliable carrier data. I'm really happy to hear the response time met your expectations and that the batch endpoint helped reduce the number of requests. Thanks for giving Numscope a try, and if you have any ideas or features you'd like to see next, I'd love to hear them! 🚀
How accurate is the carrier detection when numbers have been recently ported to a new provider? That kind of edge case tends to make or break these lookup tools.