Rakuten Mobile
Rakuten Mobile is the Japanese mobile network operator (MNO) of Rakuten Group, headquartered in Setagaya, Tokyo, and Japan's fourth nationwide carrier alongside NTT Docomo, KDDI, and SoftBank. Commercially launched in April 2020 and surpassing 10 million subscribers in December 2025, Rakuten Mobile built and operates the world's first fully cloud-native, end-to-end virtualized mobile network on Open RAN, with 4G population coverage of 99.9% and expanding 5G plus 700 MHz Platinum Band rollout. The same engineering effort spun out into Rakuten Symphony, a B2B business that productizes the Rakuten Mobile playbook as the Symworld platform — a cloud-native operating platform for telcos covering Open RAN (CU/DU/RIC, Symware distributed unit appliance), Symworld Cloud (Kubernetes-based hyperconverged telco cloud / CNP), OSS/BSS, site management, and a marketplace of pre-integrated cloud-native network functions from 50+ vendor partners. Symphony also offers Rakuten CPaaS (carrier-grade SMS, Confirm/OTP, and Short URL APIs running on the Rakuten Mobile network with JWT-authenticated REST endpoints at api.cpaas.symphony.rakuten.net) and Rakuten Communications Platform (RCP) for enterprise private 5G. Public, developer-accessible APIs are concentrated in the CPaaS suite; the Symworld platform APIs themselves are TM Forum-aligned but exposed under commercial engagement rather than a public developer signup.
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 Rakuten Mobile the way a machine reads it — 5 machine-readable artifacts across 3 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 — Rakuten Mobile scores 12.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 Rakuten Mobile
Each block below is one kind of artifact we hold for Rakuten Mobile. 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 3
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.
Rakuten CPaaS SMS / Messaging API
Carrier-grade SMS API for sending and receiving A2P and P2A SMS at scale on the Rakuten Mobile network, with delivery receipts pushed to caller-configured webhooks. UTF-8 encode...
Rakuten CPaaS Confirm (OTP) API
One-time PIN delivery and verification API for two-factor authentication and transaction confirmation, with SMS and Voice channel support, lifecycle operations for request / val...
Rakuten CPaaS Short URL API
Link shortening and analytics API for CPaaS campaigns. Supports create / retrieve / update / list / delete operations on short URLs, with JWT bearer authentication, UTC timestam...
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 Rakuten Mobile — 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
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Company 9
The organization behind the API
Scroll within the panel for all 9 ·
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/rakuten-mobile · machine-readable index on apis.io