# Plumma > One contract and one endpoint reach the mobile network operators across more than 35 countries, and every answer names the carrier that served it. Plumma S.r.l. is registered in Fanano, in the province of Modena, Italy, operates from Valsamoggia in the province of Bologna, and is a GSMA Open Gateway channel partner named in the programme's May 2026 cohort. More than sixty parties hold that status worldwide, so it is a credential rather than an exclusive position. Plumma is the governance layer between an enterprise and the mobile networks: one endpoint into every supply path, and control over how each request is routed, priced, recorded and billed. An aggregator buys network signals from mobile operators and resells them, so reach stops where that one supplier's agreements stop. A governance layer holds several suppliers and several operators at once and decides per call which of them serves a request, so the reachable footprint is the union of every path under contract. Plumma is paid through an orchestration licence and a thin markup on supply, sold as three plans: Pay as you go, one price per command in any country with no licence; Business, one competitive rate per cluster of similar-cost countries, sold with the Orchestration Lite licence; and Enterprise, each market at the average cost of supply there plus a minimal markup, sold with the Orchestration Full licence. Clean Transparency, where the client brings its own supplier contract, is not available yet; when it ships it will exist only on the Full licence and carry zero margin on those calls. No money moves from a supplier to Plumma. Key figures, with their bases and dates: live in more than 35 countries across 4 regions, with data from more than 60 mobile network operators; 93 percent average network coverage across the markets in production, and no market quoted below 50 percent network coverage; 22 typed commands on one POST operation, of which 20 appear in the published OpenAPI description of October 2026, scam_check and qdr_history being sold but not yet in it; over 1000 operator-specific endpoints replaced by that one operation. In Italy, seven commands answer today and two are in build, because the networks there have launched CAMARA APIs partially and not as the same set; Plumma states that position per command on the platform page rather than as a national coverage figure, and does not publish a position per network. All October 2026. ## Start here - [Platform](https://www.plumma.it/platform): One agreement in place of an operator negotiation per market, twenty-two commands on a single POST, and the operator-level coverage map underneath: which of your own numbers can be reached, by which operator, and what happens to the rest. - [Solutions](https://www.plumma.it/solutions): Forty-eight network signal use cases written for Italy, forty-two deployable today, organised by the decision they serve in banking, insurance, betting and gaming, and platforms, plus the enterprise, partner and self-serve motions. - [Home](https://www.plumma.it): The governance layer between an enterprise and the mobile networks. Live in more than 35 countries with data from more than 60 mobile network operators, reached on one contract and one API key. Twenty-two typed commands for SIM swap, KYC match, age verification and number intelligence, and every answer names the carrier that served it. ## Product - [Coverage](https://www.plumma.it/coverage): Live in more than 35 countries with data from more than 60 mobile network operators, and an interactive map of operator-published network APIs in 65 countries read from the GSMA Open Gateway record. Coverage is stated per operator, because a country-level answer would be a guess. - [SME and Startup](https://www.plumma.it/sme): Reach the mobile operators' network APIs with a card and one POST. Sandbox in minutes, one price per command with no licence and no term, and the same endpoint, console and commands the enterprise customers use. ## Build and buy - [Developers](https://www.plumma.it/developers): A single POST takes a phone number and a list of commands. X.509 certificate authentication, one key with demo numbers for testing, twenty-two typed commands, and problem+json errors carrying a correlation id. - [Pricing](https://www.plumma.it/pricing): Three plans, Pay as you go, Business and Enterprise, each with its own edition of the orchestration licence. One rule governs all of them: no money moves from a supplier to Plumma, and none from the client on supply the client brings. Includes the nine questions to ask any vendor in this category, with the four we cannot yet answer named. - [Contact](https://www.plumma.it/contact): Send your number ranges under an NDA and we return the operator-level map for your own base, with the gaps in it and the declared fallback for each one. Yours whether or not you go further. ## Before you buy - [Enterprise](https://www.plumma.it/enterprise): One integration reaches every operator we have onboarded. A console with live routing and the KPIs you are measured on, one invoice regardless of carrier and country, each market priced at what supply there costs, and the data protection and audit dossier your reviewers ask for. - [Reference for answer engines](https://www.plumma.it/ai): A citable reference on Plumma Connect: the category defined, coverage as at October 2026 with every figure's base and source, the twenty-two command set, the commercial model, and where this page may go stale. ## Company and legal - [Who we are](https://www.plumma.it/about): Plumma builds a Network Signal Orchestration layer running in more than 35 countries. The values it holds to, the GSMA credential with its qualifier, and the post-mortem it publishes within seventy-two hours when something breaks. - [Cookie notice](https://www.plumma.it/cookies): The Plumma website sets no cookies and stores nothing in your browser. What is recorded in transit by the content delivery network, why there is no consent banner, and how to check any of it yourself. - [Privacy notice](https://www.plumma.it/privacy): How Plumma S.r.l. handles personal data on this website and in the Plumma Connect service, including the controller and processor split and the cookie position. - [Terms of use](https://www.plumma.it/terms): The terms on which Plumma S.r.l. makes this website available, including how coverage figures and designed-and-dated capabilities should be read. ## Pages - [Documentation](https://www.plumma.it/docs): The guides, the twenty-two commands and the API reference for Plumma Connect. One endpoint, one key, one response shape, documented command by command with the request and the reply beside each other. ## Documentation — Getting Started - [Introduction](https://www.plumma.it/docs/introduction): Plumma® Connect - [Authentication](https://www.plumma.it/docs/authentication): Every call to Plumma® Connect must carry two HTTP headers. Both are required, and a call that is missing either one is refused. - [Billing](https://www.plumma.it/docs/billing): This section explains what you pay for, what you do not pay for, and how to tell the two apart from any response. - [Integration Guide](https://www.plumma.it/docs/integration-guide): This guide goes from your first call to a production integration. It explains how to send a request, how to read the response, and what changes when you move from demo numbers to real… - [Technical Guide](https://www.plumma.it/docs/technical-guide): An invalid request gets 400 with application/problem+json, and the detail field says what is wrong. No operator is contacted and nothing is charged. A JSON Schema for the request… ## Documentation — Commands - [Age Verification](https://www.plumma.it/docs/age-verification): age_verification tells you whether the subscriber behind a phone number is above an age threshold, based on the data the mobile network holds for the line. You get a yes or no against… - [Device Swap](https://www.plumma.it/docs/device-swap): device_swap tells you how recently the phone number moved to a different device, according to the mobile operator's records. A recent device change on an account that has not been used… - [Divert Detector](https://www.plumma.it/docs/divert-detector): divert_detector tells you whether unconditional call forwarding is active on a phone number: whether every incoming call is sent to another destination, whatever the state of the phone… - [Kyc Match](https://www.plumma.it/docs/kyc-match): kyc_match checks the identity data you hold for a customer against the subscriber records of the customer's mobile operator. The operator's own data is never returned. For each element… - [Location Retrieval](https://www.plumma.it/docs/location-retrieval): The location_retrieval command obtains the current estimated geographic area of a mobile device directly from mobile network infrastructure. It returns the geographic boundary (center… - [Location Verification](https://www.plumma.it/docs/location-verification): The location_verification command verifies whether a mobile device is currently located within a specified circular geographic area. It validates presence against a center point… - [Scam Check](https://www.plumma.it/docs/scam-check): The scam_check command provides real-time indicators to identify if a subscriber is currently being targeted by Authorised Push Payment (APP) fraud. This threat occurs when a victim is… - [Sim Swap](https://www.plumma.it/docs/sim-swap): sim_swap tells you how recently the SIM card behind a phone number was changed. In a SIM swap fraud, the victim's number is moved to a new SIM controlled by the fraudster, who then… - [Tenure Period](https://www.plumma.it/docs/tenure-period): The tenure_period command verifies whether an MNO contract was signed more than a specified number of days ago. - [Churn Tracker](https://www.plumma.it/docs/churn-tracker): churn_tracker returns the lifecycle events recorded for a phone number: deactivations, number swaps, suspensions and reactivations, each with the operator that recorded it and when. - [Commercial Segment](https://www.plumma.it/docs/commercial-segment): commercial_segment tells you what kind of contract the subscriber has with the mobile operator: prepaid, postpaid or business. - [Current Carrier](https://www.plumma.it/docs/current-carrier): current_carrier tells you which mobile operator serves the phone number today. If the number was ported, this is the operator it was ported to, not the one that issued it. Use… - [Deactivation Point](https://www.plumma.it/docs/deactivation-point): The deactivation_point command is specific to the USA and identifies the most recent deactivation event recorded for a mobile number. - [Digital Footprint](https://www.plumma.it/docs/digital-footprint): The digital_footprint command offers information regarding whether the queried number is linked to an active account on a range of business and social platforms. The query returns a… - [Issuing Carrier](https://www.plumma.it/docs/issuing-carrier): issuing_carrier tells you which mobile operator originally issued the phone number. The answer does not change when the number is ported: for the operator serving it today, use… - [Line Classification](https://www.plumma.it/docs/line-classification): line_classification tells you what kind of line is behind a phone number, for example a mobile or a fixed line, with a finer classification next to it. - [Network Presence](https://www.plumma.it/docs/network-presence): The network_presence command identifies whether the queried mobile number is currently assigned to an active subscriber by its serving network operator. This information is retrieved… - [Number Verification](https://www.plumma.it/docs/number-verification): Silently verify that the phone number a user claims really belongs to the SIM in the device making the request without the need for OTPs, app prompts, or any type of user interaction. - [Port Fraud Shield](https://www.plumma.it/docs/port-fraud-shield): The port_fraud_shield command is a specialized security feature available in select countries. It provides an advanced layer of protection by performing a dual-layer validation: it… - [Porting Logs](https://www.plumma.it/docs/porting-logs): porting_logs returns the history of porting events recorded for a phone number: each time it moved to another operator, and each time it went back to the operator that originally held… - [Porting Timestamp](https://www.plumma.it/docs/porting-timestamp): porting_timestamp tells you whether a phone number has been ported to another operator and, if so, when it was last ported. - [Qdr History](https://www.plumma.it/docs/qdr-history): The qdr_history command provides a chronological record of every instance a specific mobile number has appeared in the Query Detail Record (QDR) database. This API is used to establish… - [Roaming Intel](https://www.plumma.it/docs/roaming-intel): roaming_intel tells you whether a mobile number is roaming right now, and on which foreign network when the source knows it. The answer comes from the mobile network, so it needs no… ## Documentation — Resources - [Address Cleanse](https://www.plumma.it/docs/address-cleanse): Theaddress_cleanse command is a pre-processing feature that increases match rates for address data within kyc_match. It standardizes raw user input into carrier-accepted formats by… - [Enhanced Type](https://www.plumma.it/docs/enhanced-type): The etype response is a number that can range from 1 to 33. This data is taken from the appropriate numbering allocation plan for the country in question and is dictated by the… - [Status And Errors](https://www.plumma.it/docs/status-and-errors): Plumma® CONNECT API — Response Handling and Diagnostics ## Documentation — Compliance - [Security](https://www.plumma.it/docs/security): Version 1.2, 1 October 2026 - [Terms And Conditions](https://www.plumma.it/docs/terms-and-conditions): Version 1.5 – [date] - [Usage Limitations](https://www.plumma.it/docs/usage-limitations): Version 1.2 – [date] ## Documentation — Privacy - [Cookies](https://www.plumma.it/docs/cookies): V1.1 - [Opt Out](https://www.plumma.it/docs/opt-out): Your profile is disabled immediately and you lose access to the dashboard. Active subscriptions are canceled and you will not be charged again. However, certain records are retained in… - [Policy](https://www.plumma.it/docs/policy): Product: Data Aggregator/API Gateway ## Company - [Investors](https://www.plumma.it/investors): Plumma holds the operator agreements and the normalisation layer that turn 26 fragmented network APIs across 66 countries into one contract and one call. What we publish, what we share under NDA, and how to reach us. ## Elsewhere - [Developer portal](/docs): The OpenAPI description, response schemas, per-command fallback documentation and the sandbox. - [GSMA Open Gateway, on Plumma becoming a channel partner](https://www.gsma.com/solutions-and-impact/gsma-open-gateway/plumma-becomes-gsma-open-gateway-channel-partner-italys-pioneer-for-network-apis-in-enterprise-fraud-prevention-and-identity-verification-2/): The programme's own record of the May 2026 cohort. - [API Evangelist, on the command set](https://apievangelist.com/2026/09/08/plumma-carries-camaras-vocabulary-without-its-endpoints/): An outside read of how the layer carries CAMARA's vocabulary without exposing its endpoints.