Skip to content
HeuriTel
Sign in
Engineers working at a network operations desk with several screens.

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 availableLevel 2 of 5 — A journey runs end to end on sample data, including its refusal and failure states. Bought by Network, Wholesale and Enterprise. Nothing here has run against an operator system.

Open the demonstration

Engineers at a network operations desk. The capabilities and calls here are the sample's; no API is exposed and nothing is invoiced.

Public nowAnyone can do this from this page, without signing in, and the page keeps no record of it. This page, its sample workbook and the sample's review need no sign-in; the steps below say which need more.

The sample, computed

315 billable calls worth 765 KES across 3 enterprises; 60 calls refused for consent, 1490 for rate limit; 2 subscription(s) not valid.

HeuriTel default synthetic sample — Kenya, in KES, Kiswahili; sample open-gateway-metering-sample v1. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it. Configure a market and this page, the workbook and the review recompute for it.

  • 315 calls — Billable callssuccessful calls within the rate limit on valid subscriptions, consent held where required
  • 765 KES — Settlementbillable calls × price per call
  • 60 calls — Refused for consentconsent required and denied or not recorded
  • 1,490 calls — Refused for rate limitcalls in a minute above the subscription's limit
  • 0 calls — Over quotabillable calls above the monthly quota
  • 17.7 % — Success ratesuccesses over calls made

Invoice 765 KES 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 never passed the sandbox. No API was exposed or called. No consent was requested. No invoice was issued.

From this page to live operation

10 steps: 4 public now, 3 in an entitled workspace, 1 a request form, 1 needing an authorised sandbox, 1 not implemented.

Each step says who can take it today. A route existing is not the same as an action being available: the state beside each step is decided by the same rules that refuse a request.

  1. 01 · What you can buyPublic nowTurn network capability into services enterprises can buy, with operator policy and commercial control intact.All ten offers
  2. 02 · A working demonstrationPublic nowThe offer's journey on sample data.Open the demonstration
  3. 03 · The sample, as a workbookPublic now3 data sheets, a manifest and the generated guide, dictionary, validation lists and expected outputs — downloadable without signing in, in the sample's market and currency.Download the sample workbook
  4. 04 · Validation, on the samplePublic nowcapabilities, 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. The public review checks a returned workbook against the sample it was issued from, answers with the result before and after, and stores nothing.POST /api/sample/open-gateway-metering/review
  5. 05 · Acceptance and the stored simulationEntitled workspaceYour organisation's own workbook, reviewed, accepted as an immutable version with its original retained, and the engine's result stored whole — never recomputed on reopening.Open the workbench
  6. 06 · Decision and approvalEntitled workspaceA second person decides the recommendation; the maker cannot. Approval applies to a simulated recommendation.The approvals queue
  7. 07 · EvidenceEntitled workspacemetering per subscription against its quota and policy; consent refusals; settlement statement per enterprise; run register export. The register export, the retained original, the run history, the dry-run plan and the pilot package are downloadable from the workbench.Evidence on the workbench
  8. 08 · A controlled pilotPilot request availableThe request form is available here; the pilot is scoped in writing before anything runs on your systems: a CAMARA endpoint called against an operator sandbox with real consent handling. No pilot has been requested or agreed, and none is demonstrated.Request a controlled pilot
  9. 09 · Execution against your sandboxRequires an authorised sandboxThe dry-run plan names every connector call an approved decision would make across network exposure platform, consent management, enterprise billing; nothing is called and no receipt exists, because no authorised sandbox is registered.
  10. 10 · Live operationNot implementedUnder a separate production authorisation, with outcomes reconciled against your own records: calls metered against the gateway's own logs; settlement against enterprise invoices. Not built; no connector exists.
Public now
Anyone can do this from this page, without signing in, and the page keeps no record of it.
A verified sign-in sees it on sample data; it reads nothing private and stores nothing.
Entitled workspace
A member of an organisation that holds the owning product and has the journey configured; the role decides which actions.
Pilot request available
The request form is available. A pilot is scoped in writing afterwards; the pilot itself is not demonstrated.
Requires an authorised sandbox
Needs an authorised operator sandbox, which no organisation has registered. The permission that would reach one is refused to everyone.
Requires production authorisation
Needs a production authorisation from the operator and a connected operator system. No such authorisation exists.
Not implemented
No code performs this.
On demand

The contract, the data, the pilot and the products beneath.

Four things a technical or commercial evaluation asks for, each in the same terms as the other nine offers.

The offer in twelve lines
The offer, in twelve lines

The offer in the same terms as the other nine.

Read from the offer contract and the engine's own run; the same twelve fields on every offer page.

Commercial offer
Network Intelligence and Open Gateway Services
Buyer
Network, Wholesale and Enterprise
Problem
Network capability is not commercially packaged; CAMARA and Open Gateway need policy, consent and billing around them.
Outcome a pilot would count
Enterprise API contracts, and revenue per capability.
Current availability
Demonstration available — level 2 of 5: A journey runs end to end on sample data, including its refusal and failure states. Of 10 steps, 4 are public now, 3 need an entitled workspace, 2 need what does not exist yet. Public now Entitled workspace Not implemented
Public sample
HeuriTel default synthetic sample: Kenya, in KES and Kiswahili (sample open-gateway-metering-sample v1). Download the workbook. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it.
Data requirements
Capabilities (capability_id, camara_api, version, markets, consent_required, price_per_call); Subscriptions (subscription_id, enterprise, capability_id, market, monthly_quota, rate_limit_per_minute, sandbox_passed); Calls (call_batch_id, subscription_id, minute, calls, consent, outcome). 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 never echoed back.
Executable result
Engine metering-and-settlement v1, on the public sample: 315 billable calls worth 765 KES across 3 enterprises; 60 calls refused for consent, 1490 for rate limit; 2 subscription(s) not valid. 6 measures with their basis, 3 sections, 4 exceptions with owners. Recommendation: Invoice 765 KES 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 never passed the sandbox. Simulated; nothing ran against an operator system.
Approval model
Maker-checker: the person who accepted the data or requested the run cannot decide its recommendation; a client administrator does. Approval applies to a simulated recommendation.
Evidence
metering per subscription against its quota and policy; consent refusals; settlement statement per enterprise; run register export; the retained original with its inspection verdict; the run history; the per-record dry-run plan; the pilot package.
Pilot requirements
a CAMARA endpoint called against an operator sandbox with real consent handling. None is evidenced; no pilot is requested or agreed.
Live requirements
Connected under a separate authorisation: network exposure platform, consent management, enterprise billing — none connected; reconciled before any outcome is claimed: calls metered against the gateway's own logs; settlement against enterprise invoices. Not built.

Beneath the offer: Network Intelligence and Open Gateway, Revenue, Risk and Assurance, Partner and Delivery Operations, AI and Governance, CAMARA & GSMA Open Gateway APIs.

Your data — 3 sheets, checked before anything is read
Your data

3 sheets, checked before anything is read from them.

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 never echoed back.

  • 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.
A pilot’s measure and prerequisites — 4 things that would have to be true
What a pilot would count, and needs

Enterprise API contracts, and revenue per capability.

Nothing is counted until it is reconciled against your own records: calls metered against the gateway's own logs; settlement against enterprise invoices.

  • a CAMARA endpoint called against an operator sandbox with real consent handling
  • Connected under authorisation: network exposure platform. Not connected today.
  • Connected under authorisation: consent management. Not connected today.
  • Connected under authorisation: enterprise billing. Not connected today.
Built on 4 governed products and 2 catalogue streams
What it draws on

4 governed products and 2 catalogue streams.

The offer is a commercial view onto the same platform every other offer runs on. Its workbench opens with Network Intelligence and Open Gateway.