# Plumma > Plumma SRL is an Italian software house in Modena that operates Plumma Connect, an > aggregation gateway over mobile network operator intelligence. It sells enterprises one > integration point for the operator-held identity, SIM and network-state signals exposed > through the GSMA Open Gateway programme, instead of onboarding operator-by-operator and > country-by-country. Plumma is a GSMA Open Gateway channel partner. Generated by API Evangelist on 2026-09-07 from this provider profile. Plumma does not publish an llms.txt of its own (/llms.txt returns 404 on connect.plumma.it and 403 on www.plumma.it), so this file is generated, not harvested. ## What is unusual about this API Plumma Connect is deliberately not shaped like CAMARA. Where the CAMARA family publishes one endpoint per capability, Plumma Connect publishes a SINGLE OpenAPI 3.1 operation — `POST /api` on `https://connect.plumma.it/services` — taking an E.164 phone number plus a `commands` array. The CAMARA surface is an implementation detail behind that abstraction rather than the developer contract. The command vocabulary, not the URL space, is the API. Three things an agent must know before calling it: 1. **HTTP 200 does not mean success.** Every authenticated call returns 200; the real outcome is the numeric `status` inside the body (0 OK, 1 invalid number, 2 no coverage, 4 partial reply, 5 unknown error), plus a per-command breakdown appended to `status_message` and a packed `cmd_enc` bitfield. 2. **Billing is per command an operator served, not per API call**, drawn from a prepaid Euro wallet. Status 0 and 4 are billable; 1, 2 and an empty 5 are not. Five commands are *global* and are billed for every country regardless of coverage. 3. **There is no idempotency key and no rate-limit header.** A retry of a served call is a second charge, and remaining budget is not observable at runtime. ## APIs - [Plumma CONNECT API](https://connect.plumma.it/plumma-connect-docs/): one operation, `connectApi`, over 17 enumerated commands — SIM swap, KYC match, age verification, carrier and porting intelligence, roaming, digital footprint, call-divert detection and more. Base URL `https://connect.plumma.it/services`. ## Specs - [OpenAPI 3.1 (upstream)](https://connect.plumma.it/docs/openapi/connect-api.json) - [JSON Schema draft-07, request validation (upstream)](https://connect.plumma.it/docs/openapi/plmrequest.schema.json) - OpenAPI in this profile: `openapi/plumma-connect-openapi.yml` (and the verbatim JSON at `openapi/_original/plumma-connect-api.json`) - Overlay of API Evangelist annotations: `overlays/plumma-connect-api-overlay.yaml` ## Docs - [Documentation and API reference](https://connect.plumma.it/plumma-connect-docs/) - [Product site](https://connect.plumma.it) - [Company site](https://www.plumma.it) - [Console and sandbox](https://connect.ploomma.com/) - [Support](https://connect.plumma.it/support/) - [Service status](https://oneuptime.com/status-page/5c4b010b-1753-4d8f-8689-226d6e86d72a) - [Blog](https://connect.plumma.it/blog/) - [Security and compliance](https://connect.plumma.it/plumma-connect-docs/#security) - [Terms of service](https://connect.plumma.it/plumma-connect-docs/#terms-and-conditions) - [SLA and limitations](https://connect.plumma.it/plumma-connect-docs/#usage-limitations) - [Privacy policy](https://www.plumma.it/privacy-policy.html) ## Profile artifacts - Command vocabulary: `vocabulary/plumma-commands-vocabulary.yml` - Request/response data model: `data-model/plumma-data-model.yml` - Cross-cutting conventions: `conventions/plumma-conventions.yml` - RFC 7807 problem types: `errors/plumma-problem-types.yml` - In-body status registry and cmd_enc decoding: `errors/plumma-status-codes.yml` - Authentication profile: `authentication/plumma-authentication.yml` - Sandbox and demo identifiers: `sandbox/plumma-sandbox.yml` - Rate limits: `rate-limits/plumma-rate-limits.yml` - Plans and pricing: `plans/plumma-plans-pricing.yml` - Lifecycle, SLA and support tiers: `lifecycle/plumma-lifecycle.yml` - Conformance and compliance posture: `conformance/plumma-conformance.yml` - Domain security probe: `security/plumma-domain-security.yml` - Worked examples from the contract: `examples/plumma-connect-api-examples.json` - Agent skills: `skills/_index.yml` - Candidate MCP tool list (not published by Plumma): `mcp/plumma-mcp.yml` - /.well-known probe (nothing served): `well-known/plumma-well-known.yml` ## What Plumma does not publish No SDKs in any registry (the Technical Guide says the section is "under construction"), no public Postman or Insomnia collection (the guide ships the literal placeholder "LINK_HERE"), no GitHub organization, no MCP server, no A2A agent card, no `/.well-known/` documents, no webhooks or AsyncAPI ("Webhooks and asynchronous notifications: This section is under construction"), no changelog, no deprecation policy, and no per-command unit prices outside the authenticated console.