Yonsei University
Yonsei University is a private research university in Seoul, South Korea, founded in 1885 and ranked #73 in the QS World University Rankings 2025. Its public, machine-readable footprint is limited and primarily research- and library-oriented: the Yonsei Research Information portal runs on Elsevier Pure (which exposes Pure OAI-PMH and REST endpoints, but they require credentials/IP allow-listing and return HTTP 401 publicly), and the medical library operates a DSpace 5.5 institutional repository (YUHSpace) whose RSS feed is publicly reachable while its OAI-PMH/REST paths are not currently resolvable. No official, documented public developer portal or open API was confirmed; the only related GitHub presence is a student-run Google Developer Group (gdg-yonsei), not an official institutional API organization.
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 Yonsei University the way a machine reads it — 55 machine-readable artifacts across 38 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 — Yonsei University scores 44.2/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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 Yonsei University
Each block below is one kind of artifact we hold for Yonsei 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 38
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.
YUHSpace Institutional Repository (DSpace)
YUHSpace is the Yonsei University Health System / Medical Library institutional repository, running DSpace 5.5 and built through the National Library of Korea OAK distribution p...
Yonsei University activity API
The activity API from Yonsei University — 39 operation(s) for activity.
Yonsei University application API
The application API from Yonsei University — 36 operation(s) for application.
Yonsei University authorCollaboration API
The authorCollaboration API from Yonsei University — 9 operation(s) for authorcollaboration.
Yonsei University award API
The award API from Yonsei University — 37 operation(s) for award.
Yonsei University classificationScheme API
The classificationScheme API from Yonsei University — 7 operation(s) for classificationscheme.
Yonsei University concept API
The concept API from Yonsei University — 4 operation(s) for concept.
Yonsei University conferenceSeries API
The conferenceSeries API from Yonsei University — 14 operation(s) for conferenceseries.
Yonsei University contract API
The contract API from Yonsei University — 26 operation(s) for contract.
Yonsei University course API
The course API from Yonsei University — 27 operation(s) for course.
Yonsei University dataSet API
The dataSet API from Yonsei University — 30 operation(s) for dataset.
Yonsei University education API
The education API from Yonsei University — 14 operation(s) for education.
Yonsei University equipment API
The equipment API from Yonsei University — 28 operation(s) for equipment.
Yonsei University ethicalReview API
The ethicalReview API from Yonsei University — 22 operation(s) for ethicalreview.
Yonsei University event API
The event API from Yonsei University — 22 operation(s) for event.
Yonsei University externalOrganization API
The externalOrganization API from Yonsei University — 29 operation(s) for externalorganization.
Yonsei University externalPerson API
The externalPerson API from Yonsei University — 22 operation(s) for externalperson.
Yonsei University fingerprint API
The fingerprint API from Yonsei University — 3 operation(s) for fingerprint.
Yonsei University fundingOpportunity API
The fundingOpportunity API from Yonsei University — 21 operation(s) for fundingopportunity.
Yonsei University impact API
The impact API from Yonsei University — 31 operation(s) for impact.
Yonsei University journal API
The journal API from Yonsei University — 22 operation(s) for journal.
Yonsei University keywordGroupConfiguration API
The keywordGroupConfiguration API from Yonsei University — 7 operation(s) for keywordgroupconfiguration.
Yonsei University milestone API
The milestone API from Yonsei University — 24 operation(s) for milestone.
Yonsei University organization API
The organization API from Yonsei University — 34 operation(s) for organization.
Yonsei University person API
The person API from Yonsei University — 58 operation(s) for person.
Yonsei University personExpertise API
The personExpertise API from Yonsei University — 7 operation(s) for personexpertise.
Yonsei University pressMedia API
The pressMedia API from Yonsei University — 24 operation(s) for pressmedia.
Yonsei University prize API
The prize API from Yonsei University — 29 operation(s) for prize.
Yonsei University project API
The project API from Yonsei University — 33 operation(s) for project.
Yonsei University publisher API
The publisher API from Yonsei University — 18 operation(s) for publisher.
Yonsei University researchOutput API
The researchOutput API from Yonsei University — 67 operation(s) for researchoutput.
Yonsei University role API
The role API from Yonsei University — 2 operation(s) for role.
Yonsei University semester API
The semester API from Yonsei University — 8 operation(s) for semester.
Yonsei University specialization API
The specialization API from Yonsei University — 8 operation(s) for specialization.
Yonsei University studentProject API
The studentProject API from Yonsei University — 26 operation(s) for studentproject.
Yonsei University studentThesis API
The studentThesis API from Yonsei University — 26 operation(s) for studentthesis.
Yonsei University thesaurus API
The thesaurus API from Yonsei University — 5 operation(s) for thesaurus.
Yonsei University user API
The user API from Yonsei University — 7 operation(s) for user.
Scroll within the panel for all 38 ·
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Yonsei Plans Pricing
PLANSRate 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.
Yonsei 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.
Yonsei 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.
Yonsei Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Yonsei University API Rules
SPECTRALYonsei University API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Yonsei Person Structure
JSON STRUCTUREYonsei Project Structure
JSON STRUCTUREYonsei Researchoutput Structure
JSON STRUCTUREExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Yonsei 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/yonsei · machine-readable index on apis.io