How does CallerAPI prevent telecom fraud?

Five layers that share one data set: a spam phone number database you host at the switch, a live Caller ID API for per-call verdicts, Falcon to verify every INVITE next to the switch, a white-label call blocking SDK on the handset, and a DID reputation monitoring API for your own numbers. Deploy one or all of them.

Can we block spam calls at the switch level?

Yes. The spam phone number database is built for switch and SBC-level blocking: you host the list yourself, it updates every minute, carries 15 days of rolling history for 195 countries, and adds zero lookup latency to call setup. One flat fee covers every use case.

Which countries does the fraud detection cover?

195 countries. Spam and fraud detection and the spam number feed cover 195 countries, and so do caller names (CNAM), so legitimate business callers can be named instead of blocked.

Can we resell spam protection to our subscribers?

Yes. That is how most MVNO and carrier partners pay for the whole stack. The call blocking SDK ships under your brand for Swift, Kotlin, Flutter and React Native, sold to subscribers as a paid protection tier that lifts ARPU and cuts churn. Licensing is a flat fee or per subscriber per month with active call blocking.

Telecom fraud prevention

Telecom fraud prevention for carriers, MVNOs and CPaaS. Block the fraud, then sell the protection.

Talk to sales See the five layers

where each layer sits one data set

edge Falcon screens INVITEs

switch Spam number feed zero latency

per call Caller ID API verdict + name

handset Call blocking SDK your brand

your DIDs DID reputation monitor spam flags

195

countries of spam reports and business caller names in one data set.

60s

between updates, around the clock. Every layer sees the same campaign in the same minute.

15 days

of rolling history, so stale numbers age out and the list never needs cleaning.

Five layers. Pick the ones your network is missing.

Each layer stands on its own. Together they cover the edge, the switch, the call, the handset and your own number inventory.

At the switch

Spam phone number database feed

Every reported number from 195 countries, the last 15 days, hosted on your side. Block inbound at zero latency, screen outbound traffic with the same list, and keep the report evidence for regulators. One flat fee, no per-lookup bill, no matter how many places you use it.

Learn more about the feed

Per call

Caller ID API with live spam detection

One GET returns the spam verdict with complaint evidence and the business behind the number. Label calls, drop robocalls, greet verified businesses by name. CPaaS and UCaaS platforms sell it as a protection tier and raise ARPU on every seat.

Learn more about the API

On the handset

Call blocking SDK

Spam protection inside your own app in about 10 lines of code, for Swift, Kotlin, Flutter and React Native. Lookups are anonymous, so no subscriber call log can leak on our side. MVNOs sell it as a paid tier: new ARPU on thin margins, and subscribers whose phone stops ringing with scams stay.

Learn more about the SDK

Your own numbers

DID reputation monitoring API

Spam protection runs both ways. One call checks each DID you own across our reputation network and tells you if it is flagged, so you can pause it and fix it before answer rates drop. Wholesale carriers and CPaaS put it in their own dashboard as a paid feature.

Learn more about DID monitoring

At the network edge

Falcon SIP screening

Falcon runs next to your switch, verifies STIR/SHAKEN on every INVITE, and blocks numbers in the spam feed when you add it. It is open source and runs on your network. To check what the caller says after the call connects, add the voice firewall.

Learn more about Falcon

Block the fraud. Then bill for the protection.

Most partners do not buy this stack to save minutes. They buy it because spam protection is a feature subscribers pay for every month, on a network where minutes and data are commodities. The feed blocks at the switch. The SDK puts your brand on every blocked call. The API labels every leg. Same data, three places to charge for it.

Licensing fits the model: the feed for one flat fee, the SDK as a flat fee or per subscriber per month with active blocking, the API on volume tiers.

New ARPU line. A paid protection tier on every plan, without building data infrastructure.
Lower churn. Subscribers whose phone stops ringing with scams do not shop around.
Your brand on every block. CallerAPI stays invisible to the end user.
Evidence on file. Every blocked number carries a report subject and date.
Outbound screening. The same list checks originating traffic for your robocall mitigation program.

Who deploys what

A starting point. Most partners begin with one layer and add the next when the first one pays for itself.

You are	Start with	Add next	What you sell
Carrier or MVNO	Spam number feed at the switch	Call blocking SDK on the handset	Paid protection tier per subscriber
CPaaS or UCaaS	Caller ID API per call	DID reputation for customer numbers	Spam labels and number monitoring per seat
VoIP or wholesale	Falcon next to the switch	Feed on the SBC	Clean inbound as a network feature
Mobile security vendor	Call blocking SDK	Feed for the backend	Scam call blocking in the suite

Telecom fraud prevention questions

Stop the next fraud campaign

Tell us about your network and traffic. You get a deployment plan, the layers that fit, and pricing.

Plan the network layers See pricing