Site-by-site carrier selection
Send each install address as a coordinate and get measured RSRP, RSRQ and SINR per carrier and band, with reading counts so you can tell thin evidence from strong evidence.
GET /lookup · one unit per location
IoT & M2M deployments
Which carrier and band will actually work at each device site?
Before you ship a modem, a SIM profile or a truck roll, check what real phones measured at the location: carrier, band, generation and signal, from the LTE Discovery Coverage Intelligence API.
14 days free · no card · Coverage API key in a minute · US organizations
MeasuredFrom real phones, not a propagation model
Per bandCarrier, band and generation on every row
H3-nativeResolutions 3 to 10, JSON or GeoJSON
LTE + 5G NRRSRP, RSRQ and SINR with reading counts
Use cases
How IoT and M2M teams use the Coverage API
Batch-check a deployment list
Convert your sites to H3 cells and check up to 100 cells per request, so a rollout plan of thousands of meters, kiosks or sensors takes a script, not a site survey.
GET /coverage/h3 · one unit per H3 cell
Match module bands to the market
See which LTE and 5G NR bands each carrier actually runs in a market before you certify a module or pick a band-limited Cat-M or Cat-1 part.
GET /band-deployment · carrier × generation × band
Flag sites that need a backup plan
Sites with weak measured signal or insufficient evidence become a short list for an external antenna, a second SIM or a field check.
GET /lookup · one unit per location
See the data
What a measured market looks like
This is the live San Francisco sample of the LTE Discovery Coverage Intelligence API: every hexagon is an H3 cell where phones recorded LTE or 5G NR signal, coloured by the strongest P90 RSRP any carrier reached there. Your evaluation key returns the same kind of evidence, broken out per carrier and band.
- Density varies. Busy areas have deep evidence; quiet areas can be thin. Every row carries its reading count.
- No data is not no coverage. Places without enough readings come back as insufficient evidence.
- Cell identity, not site locations. The API never publishes where towers are.
- No rankings. We report measured signal per carrier and band and leave the conclusions to you.
- US only. Data and plans cover the United States and US-based organizations.
Loading measured hexagons…
Plans for IoT and M2M teams
Most fleets of sites start on Market or Region. Nationwide deployment lists fit Enterprise. Self-service plans start at $249/month with transparent unit pricing.
FAQ
Questions from IoT and M2M teams
Can I check thousands of IoT sites at once?
Yes. POST up to 100 coordinates per lookup request or up to 100 H3 cells per coverage/h3 request. Each input location or cell is one billable unit.
Does it tell me where the towers are?
No. The API reports measured signal and cell identity and channel data at your locations, not site locations.
What if there is no data at a site?
The response says insufficient evidence, which is not the same as no coverage. Density varies by area, so treat those sites as unknown and verify them another way.
More answers on the Coverage API overview, or explore other solutions:
Contact
Talk to us about IoT and M2M coverage data
Nationwide or state scope, embedded or customer-facing use, invoicing and procurement: tell us what you need and we will scope it with you.
Prefer email? support@ltediscovery.app
Ready to try it yourself? Start the free 14-day evaluation.