Company overview · 2026
Identify the network. Verify the line. Globally.
Who we are
num-iD provides real-time number intelligence and routing data to the world's leading telecom operators, messaging hubs and identity platforms. Independent, focused on telecom data only, and engineered for throughput.
About num-iD
Tier-1 enterprise customers in finance and telecom drove us to build our own MNP databases in Europe and the Americas, plus proprietary SS7 capacity for live HLR.
Pan-European bank · Global SMS aggregator · Pan-American MNO
Brought the same intelligence to aggregators, CPaaS, MNOs, contact centers and fintech / ID&V — the prospection markets you'll see throughout this deck.
Aggregator hubs · CPaaS platforms · MNOs · Fintech ID&V
What we do
A single phone number, any country, any format.
Regional PoPs, sub-second, authenticated by IP.
Normalized JSON: network, status, routing fields.
GET api.num-id.com/query/34630081191?service=mnp "oc": "ES" · "on": "TELEFÓNICA" · "pdi": true · "rc": "1-00" Who uses us
The problem
Range data points to the wrong operator.
A2P traffic billed for SMS that never land.
OTPs and logins from accounts no longer in the user's hands.
Same root cause. One API call resolves it for all three.
Our approach
A single HTTPS endpoint, normalized JSON, sub-second. One MSISDN goes in, full routing intelligence comes back.
Which network owns this number today.
Authoritative network ownership for any MSISDN, accounting for portability. Returns operator code, MCC/MNC, ported indicator, release code — everything you need to route correctly.
Is this number alive right now.
Live-network reachability against the real mobile network. Returns subscriber status, roaming context, current network — everything you need to validate before sending.
Use case · 01 · Voice routing
Range data tells you where a number was born. By the time the call connects, the subscriber may have moved networks twice. Here is what one call looks like through num-iD.
Range data says Operator A. You'd route there by default — and pay a cross-network surcharge if you're wrong.
The number was ported 14 months ago. It now lives on Operator B. We return the live MCC/MNC in under 300 ms.
No off-net surcharge. Lower PDD. Higher ASR. The call connects on first try, and the billing matches the leg.
Reference figures from a representative Tier-2 carrier mix on Western EU and LATAM routes. Actual deltas depend on traffic profile and current routing rules.
Use case · 02 · Fintech & ID&V
Every fintech journey has four high-risk moments where a phone number is the credential. num-iD becomes the guard-rail at each one.
Is the line live? Block 100% of made-up numbers before they ever reach the funnel.
Was the SIM swapped in the last 24 hours? Pause high-risk OTPs and step up.
Confirm the number is on its real home network. Stop spoofed auth before the wire moves.
Has the number been ported recently? Block password resets to just-ported lines.
~24,000 blocked fraud events / year · ~$58 avoided loss per blocked event · based on neo-bank ATO benchmarks.
vs. cost of pre-checks on 2.4M auths · net 10-20× ROI.
Illustrative scenario based on representative neo-bank fraud benchmarks. Actual numbers depend on traffic mix, risk thresholds and step-up policy.
Use case · 03 · ROI for A2P
Sample scenario based on industry benchmarks. Plus secondary gains: deliverability metrics, lower fraud, regulatory compliance.
Multi-country view · 10 emerging-market destinations
Verify catches dead and ported-out numbers before the SMS is sent. The savings shown are the SMS termination cost you don't pay for messages that would have failed anyway. Same Verify pre-check, applied across 1M queries per country.
Illustrative scenario based on representative termination rates. Per-customer mix and rates will vary. Verify priced at $0.0014 / lookup (10M+ band).
Why us
Four reasons that are concrete, not generic — and that an incumbent can't match.
Independent · engineering-first · telecom-only · data lineage you can audit.
Solutions summary
Four building-blocks behind a single GET. Pick one, pick all — the integration is the same.
How we deliver
curl -s "https://api.num-id.com/query/34630081191?service=mnp" \ -H "Accept: application/json" # Response (HTTP 201) "tn": "34630081191", "oc": "ES", "mcc": "214", "mnc": "07", "on": "TELEFÓNICA MÓVILES ESPAÑA", "rc": "1-00"
Customer portal
Every customer gets a private portal at portal.num-id.com — operate without writing tickets.
Next steps · try it now
One email. We whitelist it.
Auth by IP. No credentials in your code.
Live response from a real PoP.
Send us a sample of your real numbers. We send back the table.
curl -s "https://api.num-id.com/query/34630081191?service=mnp" \ -H "Accept: application/json" # Response (HTTP 201) · 287 ms { "tn": "34630081191", "oc": "ES", "mcc": "214", "mnc": "07", "on": "TELEFÓNICA MÓVILES ESPAÑA", "nt": "mobile", "pdi": true, "pi": false, "rc": "1-00" }
Identify the network. Verify the line. Globally.