Japan and Korea sells itself on carmakers, and its leaders are a messenger and a payment API

Japan and Korea sells itself on carmakers, and its leaders are a messenger and a payment API

The Japan & Korea region lists 322 providers and 889 APIs. Its own description names manufacturing, automotive, robotics and gaming as the reason the market matters. The scores do not follow that description. The two exemplars are LINE at 74.5 and PAY.JP at 71.8, a messaging platform and a Stripe-style yen payment API.

The top of the region

Provider Kin Score Band APIs
LINE 74.5 exemplar 12
PAY.JP 71.8 exemplar 14
TheCarApi 60.7 strong 11
3-shake 60.3 strong 6
Actionpower 59.7 strong 4
PortOne 57.8 strong 20
Dunamu 57.2 strong 2
SAKURA internet 54.1 developing 44
Soracom 50.4 developing 45

Only ten providers in the region reach strong or better. The rest of the distribution is 24 developing, 37 thin, 66 emerging and 185 minimal. That means 57% of the region scores minimal.

Where the carmakers sit

The names the description leans on are all in the bottom half. Hyundai does best of the manufacturers at 46.9, with one API. Samsung is thin at 34.1 across 12 APIs, and Toyota is thin at 31.1 across 14. Sony is emerging at 17.4. Nissan scores 9.1 and Honda 8.9, both minimal. Nintendo, the region’s best-known gaming name, has zero APIs and scores 8.5.

The consumer platforms are not much better. Rakuten lists 33 APIs and scores 29.8. Kakao lists 21 and scores 27.2. Naver lists 18 and scores 11.6. Having a lot of APIs does not lift the score when the contracts, auth documentation and machine-readable artifacts are missing.

The infrastructure companies do the opposite. SAKURA internet (44 APIs) and Soracom (45 APIs) have the two largest surfaces in the top tier, and both sit in developing. That is a cloud host and an IoT connectivity provider. They publish many APIs, and they also publish what an integrator needs to use them.

What is ours to fix

The region admits providers on three signals: 286 come in on a tag, 99 on a headquarters match and 20 on a name pattern. The name patterns pull in Toyota twice. One entry is toyota with 14 APIs, and the other is toyota-motor-corporation with zero APIs and a 2.8 score. Both are counted in the 322. TheCarApi, third in the region, aggregates auction listings and European retail classifieds and is admitted on a tag, not on its headquarters.

Takeaway

In Japan and Korea, the APIs you can build on today are messaging, payments, cloud and IoT connectivity, not the industrial names the region is known for. If you need automotive data from the region, expect to work from documentation rather than contracts. The full list is at apis.io/regions/japan-korea/.

← Defense has 360 providers, and the primes publish nothing a builder can call
Messaging and notifications is led by a service AWS stopped supporting on October 30 →