Validation per subscription
Availability in the market and sandbox conformance, before any call is billed.
4 rows · Subscription · Enterprise · Capability · Market
Bought by Network, Wholesale and Enterprise
Turn network capability into services enterprises can buy, with operator policy and commercial control intact.
Network capability is not commercially packaged; CAMARA and Open Gateway need policy, consent and billing around them.
Demonstration available — A journey runs end to end on sample data, including its refusal and failure states. Runs today on a sample of your market; its workspace opens with Network Intelligence and Open Gateway.
The result, on the sample
315 billable calls worth 765 units across 3 enterprises; 60 calls refused for consent, 1490 for rate limit; 2 subscription(s) not valid.
Sample. Choose your market to see this page, the workbook and the review in your currency and language.
Network Intelligence and Open Gateway ServicesYour market · units
315 billable calls worth 765 units across 3 enterprises; 60 calls refused for consent, 1490 for rate limit; 2 subscription(s) not valid.
Billable calls315calls
Settlement765units
Success rate17.7%
Refused for consent60calls
Decision Invoice 765 units across 3 enterprises on billable calls; suspend 2 subscription(s) until valid; review the 0 batch(es) with no consent record before any further exposure. If nobody acts: Every call the gateway logged is invoiced, including calls without consent, calls over the rate limit and calls on subscriptions that failed the sandbox.
The other 2 measures the run holds
- 0 calls — Over quotabillable calls above the monthly quota
- 17.7 % — Success ratesuccesses over calls made
See the product
The workspace, screen by screen.
The 7 screens a demo walks through, captured from the built product on sample rows. Sign in to run it on your own market and your own numbers.
1 of 7 · Overview The workbench: the tiles, the run, the ladder, the last run and the next step. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
2 of 7 · Sample The result on the sample: the headline and the tiles, each with its basis. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
3 of 7 · Sample The decision the engine proposes, and what happens if nobody acts. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
4 of 7 · Sample The checks the engine refused, each with its reason and its owner. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
5 of 7 · Your data Your data: the sheets, the template to download, and the review of what comes back. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
6 of 7 · Runs Every run, as it was computed, with the version it ran on. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
7 of 7 · Decide The proposal to an approver, and what the approver sees. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows.
Three things it decides
Each on your rows, each with its reason written.
Metering per subscription
Calls made, refused, billable, against quota.
4 rows · Subscription · Enterprise · Calls · Successes
Settlement per enterprise
What each enterprise would be invoiced, on the sample.
3 rows · Enterprise · Calls · Billable · Amount (units)
What it needs from you, and how a pilot proves it
Enterprise API contracts, and revenue per capability.
capabilities, subscriptions and calls as three sheets: every capability names an API and the markets it is available in; every subscription names an enterprise, a capability and a quota; every call names a subscription and a consent state. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused, and the refusal names the column.
- The data you supply
- Capabilities, Subscriptions, Calls — your own rows, on your own subject keys, through the same review the sample passes. Bring your data — the workbook out and back, after sign-in. Download the sample workbook
The 3 sheets, column by column
- Capabilitiesthe exposed APIs: which CAMARA capability, where it is available, whether a call needs consent, what a call costs. Columns: capability_id, camara_api, version, markets, consent_required, price_per_call.
- Subscriptionsenterprise contracts: capability, market, quota, rate limit, sandbox conformance. Columns: subscription_id, enterprise, capability_id, market, monthly_quota, rate_limit_per_minute, sandbox_passed.
- Callsthe metering ledger: calls per subscription per minute, with consent and outcome. Columns: call_batch_id, subscription_id, minute, calls, consent, outcome.
- The measure
- Counted once reconciled against your own records: calls metered against the gateway's own logs; settlement against enterprise invoices.
- The approval
- A second person approves; the person who loaded the data cannot. The decision is audited with its reason.
The products and the streams it draws on
Runs on Network Intelligence and Open Gateway; draws on Revenue, Risk and Assurance, Partner and Delivery Operations, AI and Governance and the CAMARA & GSMA Open Gateway APIs, Network Investment & Intelligence streams of the catalogue. The lifecycle to live operation and the twelve-line contract are in the workbench, after sign-in.
See it on your own numbers.
Sign in with your work email; the sample is generated for your market and currency; change the values and run again. Or book a demo and we walk it with you.