C·01
Plans and SKUs
A commercial catalog on top of the API: segments, units and plan matrices per contract, without redesigning the backend for every commercial change.
Product · 01
Entitlements
The commercial layer for APIs: plans, quotas, licenses and metering for anyone selling connectivity as a product. CAMARA (GSMA)-aligned surface, designed for operators with carrier-grade standards.
Capabilities
Everything an API needs to be sold.
Exposing a service is easy. Selling it — with plans, limits and contracts — demands an explicit commercial layer. That is Entitlements.
C·02
Quotas and metering
Every call counts. Consumption is metered against the plan and limits are enforced consistently and auditably.
C·03
Contract-based licensing
What each tenant may use, defined in the contract and enforced at runtime. No implicit access, no inherited permissions.
C·04
Feature flags
Enable functionality per plan, per tenant or per market, without deploying new code or coordinating maintenance windows.
C·05
Trials and upgrades
Trials, plan upgrades and downgrades as first-class operations — not exceptions your engineering team fears.
C·06
CAMARA standard (GSMA)
Public surface conformant to CAMARA Commonalities: common error model, trace correlation, OAuth2/OpenID with scopes and SemVer versioning. One dialect for the operator's entire API ecosystem.
How it works
From catalog to billing, in three moves.
- 01
Define the catalog
Plans, quotas and licenses are declared per contract. The commercial catalog stops living in spreadsheets and becomes part of the system.
- 02
Connect your APIs
Every request is checked against the tenant's entitlement and metered against its plan — in real time, auditably.
- 03
Grow without redesigning
New plans, markets or SKUs are catalog changes, not architecture changes. The business moves at contract speed.
{
"tenant": "operator-demo",
"plan": "connectivity-m",
"entitlements": {
"api.sms.send": { "quota": "250000/month", "used": 184203 },
"api.did.reserve": { "quota": "1200", "used": 914 }
},
"licensed_features": ["premium-routes", "audit-reports"]
}Illustrative example of the data model, not a real API response.
Questions
What we usually get asked.
What exactly is an entitlement server?
The layer that decides what each API client may consume, in what quantity and under which plan. It is the difference between exposing a service and selling it as a product.
Who is it for?
Operators and platforms that sell connectivity or APIs as a product and need fine commercial control: consistent plans, quotas, licenses and metering.
What state is it in?
Under construction on the group's sovereign infrastructure. The design follows the operator's engineering discipline and is validated in real use first.
How does it integrate?
As a service on the API path: per-call verification and metering, with explicit contracts. It does not require adopting the rest of the platform.
What is CAMARA and why does it matter?
CAMARA is the GSMA initiative standardizing telco APIs — common errors, security, versioning and semantics for SMS, Number Verification, SIM Swap and more. Conformance means a partner or peer MNO integrates our APIs without learning a proprietary dialect.
Who is behind it?
Mobiconnect, the AI and high-tech platform of Inversiones Bucardo Zúñiga — the same group that builds and operates Airtime Connect.
Contact
Talk to the people who build.
Founder-led contact: direct technical conversations with the people who design and operate the platform. No funnels, no intermediaries.
Start a conversation