Telecom
New entrants are coming into the market, and banks, fintechs and enterprises want network capabilities as APIs. Revenue from them depends on an API layer that is production-grade, documented and governed. We build it on Apigee.
Updated October 19, 2026
A network is only an asset when someone else can use it without calling you.
Billions are in the network. Enterprise customers and partner developers want its capabilities, such as identity checks, location and quality on demand, through APIs, the way they use any cloud service. Industry programs such as CAMARA and GSMA Open Gateway are already shaping what they expect.
Open access
The Konektadong Pinoy Act lowers the barriers for data transmission providers and points toward shared and wholesale access. Partners and enterprise buyers will have more networks to choose from.
What waiting costs: the partners build on the operator whose network is easiest to buy through an API.
Fraud
The SIM Registration Act ties numbers to people, and banks fighting account takeover want to check a SIM swap or verify a number in real time, the way the GSMA Open Gateway and CAMARA programs describe it.
What waiting costs: fraud prevention revenue that goes to whoever exposes those checks first.
Subscriber data
Under the Data Privacy Act and its rules, a breach goes to the National Privacy Commission within 72 hours, and the Commission can ask which system released what. Partner APIs built one deal at a time cannot answer.
What waiting costs: a notice written without the trail to support it.
| Regulator or law | What it asks | What it means for an agent |
|---|---|---|
| National Telecommunications Commission | Regulation of telecom services and providers, including quality of service and consumer protection. | Agents in care and network operations act inside the service rules and log every action that affects a subscriber. |
| DICT, Konektadong Pinoy Act (Republic Act 12234, 2025) and its implementing rules | Open access in data transmission, with registration of providers and rules on infrastructure sharing. | Wholesale and partner APIs need a catalog, an identity for every caller and metering that holds up when access is shared. |
| SIM Registration Act (Republic Act 11934, 2022) | Registration of SIMs to verified users, with confidentiality of registration data. | Number and identity checks expose only a yes or no to a partner, never the registration record. |
| Data Privacy Act of 2012 and the National Privacy Commission | Lawful processing of subscriber data, data subject rights and breach notice within 72 hours. | Network APIs release only the attributes the purpose and consent allow, and every release is logged. |
The network capability is real. The product around it is not: no catalog, no developer onboarding, no metering finance accepts, and no policy layer between partners and the core.
Can a partner developer go from sign-up to a metered, billed API call without a ticket to your engineers?
From partner sign-up to billed API call
Without
The chain stops before the invoice.
With
Sign-up to invoice, each step lit in turn.
Operators that open the network first become the platform partners build on. We start with one partner API product and finish it end to end before opening the next.
Catalog, developer portal, onboarding, quotas and policy.
You hold: a portal and gateway in production with an owner for every API product.
Apigee and APIsUsage metering on Apigee, usage events streamed to BigQuery, billing integration and anomaly detection from the first sprint.
You hold: usage records that match invoices, and alerts for traffic outside the pattern.
Vertex AI, BigQuery and dataAgents on Gemini Enterprise with the gateway in front, acting inside policy, fed by network events.
You hold: one agent in production in care or operations with a decision log.
Gemini Enterprise and agentsEasy to start
Choose one workflow, name one owner, and give us time with the people who sign it off.
We bring engineers and the gateway design, we work inside your environment under your security rules, and we write the review pack alongside the build.
A good first workflow is one fraud check a bank will pay for, such as number verification, from onboarding to invoice. See the fixed-price ways to start.
What the work feels like
One workflow is chosen and one person owns it. The questions your reviewers will ask are written down before any build starts. Your finance team sees metering reconcile in the first sprint demo.
Governance goes in before the first agent does: the gateway, the audit trail and the access rules. Your risk team sees them working.
A working demo you can show your own review board, not a status slide.
A decision log that can rebuild any action, and a go-live date that was agreed at the start.
Seen it before
Production readiness check
A short readiness check on a live or planned agent workflow. You get a score and the principles worth another look.
Take the readiness checkWe build on the portal you have where it works, and design a new one on Apigee where it does not.
Yes. Integration with billing and usage systems is part of the first sprint, not a later phase.
They sit behind the same gateway as partner traffic, so one policy and one log cover both.
It opens data transmission to more providers, so more of your traffic and partners will arrive through wholesale and partner interfaces rather than your own retail channels. We do not advise on the law itself; we build the API layer that lets you sell, meter and govern that access.
Tell us what you are working on. Our Customer Partnership Team will reply to arrange a conversation.
Get answers to your questions
AI assistant. It can make mistakes, so check anything important with our team.
