KDDI
KDDI Corporation is a Japanese multinational telecommunications operator headquartered in Tokyo, providing mobile, fixed-line, broadband, and enterprise ICT services. KDDI markets its consumer mobile services under the au brand, alongside UQ mobile and povo, and serves enterprise customers globally through KDDI Global and KDDI America. The company operates the KDDI Open API for Developers portal exposing inquiry-gated product APIs including the au PAY Mini App platform, an XR/MEC low-latency application API, a PPM consent management API, and an au mobile Identification Support Service for KYC/identity verification. KDDI also runs the au OPEN DEVICE DEVELOPER SITE for cellular module device certification, and a KDDI Cloud Platform Service knowledge site with developer API references for cloud infrastructure. In 2025 KDDI became an equity partner in Aduna, the GSMA/Ericsson-backed network API venture aggregating CAMARA-aligned carrier APIs (Number Verify, SIM Swap, Quality on Demand, Device Location) across global operators. Public OpenAPI specifications are not openly published; API access is provided through contact/inquiry workflows after partner onboarding.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles KDDI the way a machine reads it — 1 machine-readable artifact, 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 — KDDI scores 9.2/100 (minimal), 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 KDDI
Each block below is one kind of artifact we hold for KDDI. 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.
Security Posture 1
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 KDDI — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Company 5
The organization behind the API
Other 10
Properties that don't map to a standard resource type
Scroll within the panel for all 10 ·
← All providers · Data indexed from github.com/api-evangelist/kddi · machine-readable index on apis.io