Telecom and media
Enterprise customers and partner developers want network capability through APIs. We build that API layer on Apigee, inside the security obligations of your license and the PDPA, with metering your finance team can reconcile. Media and streaming services need the same layer when a live event brings the whole audience at once.
Updated October 22, 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.
Network APIs
Enterprises and developers in Singapore expect identity checks, location and quality on demand through standard APIs, the way they buy any cloud service, and industry programs such as CAMARA and GSMA Open Gateway are shaping what they expect.
What waiting costs: the ecosystem forms around the operator that opened first.
Security
Telecom licensees carry IMDA's security obligations, the major internet service providers follow the Telecommunications Cybersecurity Code of Practice, and info-communications is a critical sector under the Cybersecurity Act. A partner API or an agent is a new path in.
What waiting costs: the API product waits at security review while the partner signs with someone else.
Subscriber data
Care and retention agents read account, usage and location data. The PDPA and the PDPC's guidelines on personal data in AI systems ask for a purpose, notification and accountability for each use.
What waiting costs: a care assistant that cannot show what it read, after a complaint reaches the regulator.
Media and streaming
Matches, concerts and new releases send sign-in and subscription requests through the same APIs in the same minutes, and viewing data is personal data under the PDPA.
What waiting costs: an outage during the moment your viewers waited for, and a viewing history you cannot account for.
| Regulator or law | What it asks | What it means for an agent |
|---|---|---|
| IMDA, as telecom regulator under the Telecommunications Act | License conditions, including service and security obligations | Partner and agent access to network functions runs through a policy layer the licensee controls. |
| Telecommunications Cybersecurity Code of Practice (IMDA, applied to major internet service providers) | Measures to prevent, protect against, detect and respond to cyber threats, with incident reporting | Gateway logs and agent actions feed the same incident process as the network. |
| Cybersecurity Act 2018, as amended in 2024 (Cyber Security Agency of Singapore) | Duties for owners of critical information infrastructure, including in info-communications | An agent that touches a designated system sits inside that system's controls and audits. |
| Personal Data Protection Act and the PDPC's advisory guidelines on AI | Purpose, notification, protection and accountability for subscriber data, including when it feeds AI | The care agent reads only the fields its purpose allows, and the log shows which. |
| IMDA Model AI Governance Framework for Agentic AI (January 2026) | Voluntary guidance: bounded autonomy and access, human checkpoints, technical controls | Plan changes, credits and refunds above a set limit wait for a person. |
| IMDA, as media regulator, including the Broadcasting Act and its codes for online services | Content standards, age-appropriate access and user safety measures for media and online services | Recommendation and service agents respect each title's classification and age settings, and their actions are 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 partner API product, 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.
The code applies to the licensees IMDA designates, today the major internet service providers, so it depends on your license. Either way we design the partner API layer to its controls, because your security office and your auditors will ask the same questions.
Yes, in the API, data and AI layer around them: sign-in and subscriptions, audience data and service agents, governed under the PDPA. Content delivery systems stay where they are.
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.
