South Korea
KoreaSouth Korea
Providers using this tag (138)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 5 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 27 Early or largely undocumented
Minimal 80 Almost no public developer surface
APIs with this tag (22)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Strong 1 Solid coverage with minor gaps
Thin 9 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 4 Almost no public developer surface
Companies reaching this through an API (1)
These companies publish an API, specification or operation carrying “South Korea” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| Korea MyData (licensed MyData operators, authentication bodies and information providers) | 92% |
Cohort brief
Auto-generatedThe 119 providers in the APIs.io catalog tagged South Korea, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 57.2 | 59.1 | -1.9 | 119 |
| Contract Governance | 6.2 | 9.7 | -3.5 | 119 |
| Operational Transparency | 7.7 | 13.2 | -5.5 | 119 |
| Contract Quality | 10.1 | 18.6 | -8.5 | 119 |
| Developer Ergonomics | 14.7 | 24.5 | -9.8 | 119 |
| Access Clarity | 17.9 | 30 | -12.1 | 119 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 17% | 18% | -1 |
| MCP server (first-party) | 15% | 16% | -1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 8% | 13% | -5 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 1% | 1% | 0 |
| Governance rules | 17% | 36% | -19 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Actionpower 58.9
- 2 TheCarApi 58.4
- 3 Dunamu 58.1
- 4 공시.ai 56.7
- 5 PortOne 56.5
- 6 Ab180 52.8
- 7 Decision Anchor 52.7
- 8 Hyundai 49.5
- 9 한국주식데이터 (aikstockdata) 49.1
- 10 SK Telecom 43.8
- 1 공시.ai 51.6
- 2 Decision Anchor 51.6
- 3 ADRO 49.6
- 4 Dunamu 47.2
- 5 SK Telecom 43.4
- 6 Korbit 43.2
- 7 PortOne 40.4
- 8 한국주식데이터 (aikstockdata) 40.1
- 9 Ab180 37.3
- 10 Barogo 36.6
Coverage caveat. 109 of 119 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.