Hanyang University
Hanyang University is a private research university in Seoul and Ansan (ERICA), South Korea, ROR https://ror.org/046865y68. Unusually for this cohort it operates a genuine, institution-built API programme rather than a set of vendor tenancies: the HYU Open API Developer Center at api.hanyang.ac.kr publishes REST endpoints returning XML or JSON across twelve service categories (academic records, campus life, administration, research, careers, library, alumni giving, volunteering and more), backed by its own OAuth 2.0 authorization server, Android and iOS SDKs, an API console, a developer community and a full published error-code table. The catch is that the API catalogue itself is member-only: /api/search.page renders an empty template to anonymous visitors and app keys are issued only after manual administrator approval, so no endpoint list, scope list or machine-readable contract is publicly enumerable. The one openly callable institution-operated API is the OAI-PMH 2.0 interface on Hanyang's own DSpace repository at repository.hanyang.ac.kr, which answers Identify, ListMetadataFormats and ListSets correctly but returned noRecordsMatch to every harvest request probed. Its research-output and thesis surfaces are vendor tenancies (ScholarWorks/Bwise, KERIS dCollection), it registers DOIs through eight institute-level Crossref memberships rather than centrally, and it publishes no SAML identity-provider metadata to KAFE or eduGAIN while eleven of its Korean peers do.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Hanyang University the way a machine reads it — 13 machine-readable artifacts across 1 API, 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 — Hanyang University scores 31.4/100 (thin), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Hanyang runs a real, institution-built Open API programme, but its API catalogue is behind a developer-center member account. /api/search.page returns HTTP 200 with the detail template rendered and no rows; /develop/console.page, /notice/list.page and /board/list.page all return the login form instead of content; app keys require manual administrator approval. The public documentation pages (getting started, authentication, error codes, app registration, Android/iOS SDKs, terms of service) are readable and were the source for the authentication, errors and rate-limit artifacts in this repo, but no endpoint, no scope name and no machine-readable contract can be enumerated from outside. The one openly callable institution-operated API found is the OAI-PMH interface on the university's own DSpace host, and it returns noRecordsMatch to every harvest request. Nothing here is blocked at our end; every probe below ran and returned.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Hanyang 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.
What we probed
https://api.hanyang.ac.kr/develop/start.page→ HTTP 200https://api.hanyang.ac.kr/api/search.page→ HTTP 200https://api.hanyang.ac.kr/develop/console.page→ HTTP 200https://api.hanyang.ac.kr/develop/auths.page→ HTTP 200https://api.hanyang.ac.kr/develop/errorcode.page→ HTTP 200https://api.hanyang.ac.kr/openapi.json→ HTTP 404https://api.hanyang.ac.kr/.well-known/oauth-authorization-server→ HTTP 404https://repository.hanyang.ac.kr/oai/request?verb=Identify→ HTTP 200https://repository.hanyang.ac.kr/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc→ HTTP 200https://www.hanyang.ac.kr/llms.txt→ HTTP 404
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Hanyang University's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hanyang/"
title="Hanyang University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hanyang.svg"
alt="Hanyang University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/hanyang/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hanyang/"
title="Hanyang University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hanyang/card.svg"
alt="Hanyang University Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Hanyang University
Each block below is one kind of artifact we hold for Hanyang University. 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 7
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.
Hanyang University Open API Developer Center
Hanyang University's own Open API platform, built and run by the university rather than bought from a vendor. REST endpoints under https://api.hanyang.ac.kr/rs/ return XML or JS...
Repository at Hanyang University — OAI-PMH
OAI-PMH 2.0 metadata-harvesting interface on Hanyang's institutional DSpace repository, plus an OpenSearch 1.1 descriptor and RSS/Atom feeds. Twelve metadata formats are adverti...
Hanyang University Open API SDKs
Software development kits published by the Hanyang University Developer Center for building against the Open APIs — Android and iOS SDKs and server-side sample integrations (ASP...
Hanyang ScholarWorks (research-output tenancy)
Hanyang University's current research information system and research-output portal, run as a tenancy on the Bwise ScholarWorks platform, one instance per campus. Linked from th...
Hanyang dCollection (thesis and dissertation tenancy)
Online submission and access for Hanyang University theses and dissertations, hosted on the KERIS dCollection platform. Recorded as a relationship only; no public machine-readab...
Crossref DOI registration (institute-level memberships)
Hanyang registers DOIs through Crossref at the research-institute level rather than centrally. Members and prefixes verified on 2026-09-01: Hanyang University College of Medicin...
ROR registration
Research Organization Registry identifier for Hanyang University, the stable machine-readable identity other systems resolve the institution by.
Scroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hanyang Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Hanyang Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Hanyang Context
JSON-LDSecurity 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 Hanyang University — 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
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hanyang · machine-readable index on apis.io
This is an independent, third-party profile of Hanyang University, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.