Sungkyunkwan University

Re-profiled 2026-09-01 under the university pipeline, with the operator axis settled before anything was saved. Sungkyunkwan University publishes no public, documented developer API and no open-data portal, and that absence was established by negative probe rather than assumed: api.skku.edu, developer.skku.edu, data.skku.edu, open.skku.edu, research.skku.edu, repository.skku.edu, dspace.skku.edu, scholarworks.skku.edu, hpc.skku.edu and status.skku.edu all fail to resolve, and www.skku.edu returns 404 for llms.txt, .well-known/security.txt and .well-known/openid-configuration. Every consumable system SKKU runs is behind enrolment authentication — Kingo Portal SSO, iCampus, sugang.skku.edu course registration, the library discovery layer — which is why the state is `gated` rather than `none`: real surfaces exist, and none of them is reachable without credentials. The two exceptions were probed and are recorded: the SAML 2.0 identity provider metadata for kafe.skku.edu, which is public and machine-readable through the eduGAIN aggregate, and the OAI-PMH 2.0 provider at pure.skku.edu, which is public and unauthenticated but is an Elsevier Pure tenancy and is credited as such, not as SKKU engineering. The Pure Web Service itself (pure.skku.edu/ws/api) returns 401 and its documentation canonicalises to api.elsevierpure.com, so even the tenant has no publicly reachable programmable interface there. Deliberate exclusions, each with a reason: github.com/GDG-SKKU is a Google Developer Group student chapter publishing student project code, not SKKU's engineering, so the previous profile's institutional GitHub pointer has been removed rather than re-credited; github.com/skku exists but holds zero repositories and carries no name, description or website, so it is not evidence of an institutional presence; skku.dcollection.net is a KERIS dCollection tenancy whose robots.txt disallows all crawling and whose /oai, /srv/oai and /oai/request paths return the site's HTML shell with HTTP 200 rather than an OAI-PMH response, so it is recorded as a relationship and explicitly not as a harvesting surface; no ORCID institutional membership was found, and the 7,574 public ORCID records naming SKKU as an affiliation are a fact about researchers, not a membership. Language was a real factor and was worked around rather than reported as a barrier: the AI guidance site, the privacy policy, the netizen ethics code and course registration exist only on the Korean surface and were probed there. No specification was saved for any surface in this repository, because SKKU operates no contract of its own and every contract that touches it belongs to a vendor.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Sungkyunkwan University's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.

If this is out of date, tell us on the provider's repo and we will re-run the profile.