Coverage
What Plumma can reach
The reachable footprint is the union of every path under contract, not the footprint of one wholesale agreement. It grows as we add supply, and nothing changes at your end when it does.
Coverage
We answer coverage by hand, for now.
The country table that used to sit here was read from a public record, and it went out of date between reads. Until it reads from our own systems there is no table on this page. Tell us the markets you operate in and we answer with the commands live in each one, on whose supply, and the behaviour where nobody can answer.
Versions
Two networks in one market can run different versions.
The same command can arrive on two networks in the same country on two versions of one specification: two payloads, two error vocabularies, two sets of edge cases, and a different answer to the same question. Knowing that a signal exists somewhere in a market says nothing about what reaching every line in that market costs. That work is what you are buying.
The denominator rule
Coverage is counted per network.
A subscriber on the one network that has not shipped a command is unreachable in a country that counts as live. So Plumma counts coverage per network rather than per country, a percentage never ships without the base it is a percentage of, and where nobody can answer, the behaviour is declared in advance rather than left to a timeout. The perimeter grows. What it covers on any given day is stated exactly, per command and per market.
The work between
From published to usable.
What you inherit
- A contract per operator, per market
- An auth scheme per operator
- A payload shape per version
- A silent negative when nobody can answer
- A renegotiation every time an operator moves
What we carry
- One contract and one credential
- One request shape, whatever answered
- One response shape, whatever answered
- A declared gap, never a false negative
- Version drift absorbed behind the layer
Reach
What we can call today.
35
markets ready to call today, each with at least 50% network coverage
22
commands, each returning different data, from SIM swap and KYC match to number verification
1
single endpoint, one contract and one integration, whatever the market or the operator behind it
Commands and coverage
Write to us for what is live in your markets.
Name the markets and we send the commands live in each one, on whose supply, and what happens where nobody can answer. Send a CSV of numbers in E.164 form, with nothing else attached to them, and we return which operator holds each one, which commands that operator answers today, and which of your numbers nothing can reach. No quote until you ask for one.