Singtel
Singtel (Singapore Telecommunications Limited) is Singapore's largest mobile network operator and the anchor communications group of Southeast Asia, with a regional footprint that includes Optus in Australia and associate stakes in Airtel, AIS, Globe and Telkomsel. In the network-API value chain Singtel sits on the supply side: it owns the mobile network signals — SIM, line, device, location, call state — that the CAMARA specifications turn into callable APIs, and it packages them for Singapore as SingVerify, a five-API anti-fraud and identity suite built on the GSMA Open Gateway framework. It also operates Paragon, its own 5G/edge/network orchestration platform, which powers the Bridge Alliance API Exchange (BAEx) federating network APIs across Bridge Alliance member operators, and it is one of the twelve carrier equity partners in Aduna, the Ericsson-led joint venture that aggregates operator network APIs into a single global commercial channel. Its API posture, however, is partner-gated and sales-led: as of July 2026 there is no first-party developer portal (developer., developers., docs. and opengateway. subdomains do not resolve), no published OpenAPI, no sandbox, no SDKs and no self-serve signup. Every SingVerify and CPaaS API page on singtel.com terminates in an enterprise enquiry form, and the BAEx portal is an explicit login wall for approved partners. Developers reach Singtel's network capabilities through aggregators — Aduna and its platform partners (Vonage, Sinch, Infobip, Google Cloud), the Bridge Alliance exchange, or identity vendors such as IPification — rather than directly from Singtel. Two surfaces do exist and are captured here: www.singtel.com publishes a first-party llms.txt family (root plus consumer, support and corporate companion files, last updated 2026-06-30) that indexes its marketing and support estate for AI systems while naming none of its APIs, and Singtel runs a footer-linked vulnerability disclosure programme at vdp.singtel.com and on HackerOne. api.singtel.com is a live Apigee gateway behind Imperva that answers every unrouted path with an Apigee fault envelope — a real gateway with nothing publicly bound to it.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Singtel the way a machine reads it — 9 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Singtel scores 17.4/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Singtel
Each block below is one kind of artifact we hold for Singtel. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SingVerify Number Verify API
Network-based verification that the mobile number a user declares is the number of the SIM the request is actually coming from, used to replace or reinforce SMS OTP. Singtel doc...
SingVerify SIM Swap API
Real-time signal indicating whether the SIM bound to a mobile number has been changed recently, so that a relying party can block account-takeover attempts that rely on intercep...
SingVerify Device Location API
Verifies whether a mobile device is within an expected area or country at the time of a login or transaction, using network-derived location rather than handset GPS. Maps to the...
SingVerify Device Roaming API
Reports whether a subscriber's device is currently roaming outside Singapore, used as a risk signal in fraud and authentication decisions. Maps to the CAMARA Device Roaming Stat...
SingVerify Scam Sniffer API
Detects whether a user is on an active voice call at the moment they attempt a high-value transaction, a signal used to interdict authorised-push-payment and social-engineering ...
Singtel CPaaS SMS API
Application-to-person SMS sending and receiving for business applications, sold as part of the Singtel CPaaS portfolio. The public page describes the capability and benefits but...
Singtel CPaaS Voice API
Programmable voice / VoIP calling embedded into business applications, sold as part of the Singtel CPaaS portfolio. As with the SMS API, the public page is a product description...
Scroll within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Singtel — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/singtel · machine-readable index on apis.io