KU Leuven
KU Leuven (Katholieke Universiteit Leuven) is a research university in Leuven, Belgium, founded in 1425 and ranked #45 in the QS World University Rankings 2025. It maintains a documented public developer footprint through its ICTS Data Services, which expose REST APIs for person/who-is-who information, curriculum information, organizational-chart data, research information, educational offerings, and job vacancies, alongside an OAuth-protected individual timetable API. KU Leuven also operates the Research Data Repository (RDR), a Dataverse-based institutional repository whose REST API is publicly reachable, and runs an active official GitHub 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 KU Leuven the way a machine reads it — 59 machine-readable artifacts across 41 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 — KU Leuven scores 39.0/100 (thin), with a separate agent-readiness read of 39/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.
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.
How we profile KU Leuven
Each block below is one kind of artifact we hold for KU Leuven. 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 41
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.
KU Leuven Person Information API
ICTS Data Services REST API exposing public personnel / who-is-who person information. An expanded intranet variant requires a service account.
KU Leuven Educational Offering (Onderwijsaanbod) API
ICTS Data Services REST API exposing public educational offering data, including programs (opleidingen) and course components.
KU Leuven Organizational Chart (Organigram) API
ICTS Data Services REST API exposing public organizational-structure information matching the institutional organizational chart. An expanded intranet variant is available via s...
KU Leuven Vacancies (Vacatures) API
ICTS Data Services REST API exposing public job vacancy / job posting data.
KU Leuven Individual Timetable (Uurrooster) API
ICTS Data Services API exposing an individual's personal timetable. Protected by OAuth 2.0 (authorization code grant) with SAML as a fallback; OAuth client credentials are issue...
KU Leuven Access API
The Access API from KU Leuven — 23 operation(s) for access.
KU Leuven addFilesToDataset API
Uploads a set of files to a dataset
KU Leuven addFileToDataset API
Uploads a file for a dataset
KU Leuven addGlobusFilesToDataset API
Uploads a Globus file for a dataset
KU Leuven Admin API
The Admin API from KU Leuven — 131 operation(s) for admin.
KU Leuven Batch API
The Batch API from KU Leuven — 3 operation(s) for batch.
KU Leuven Builtin Users API
The Builtin Users API from KU Leuven — 4 operation(s) for builtin users.
KU Leuven Datasetfields API
The Datasetfields API from KU Leuven — 1 operation(s) for datasetfields.
KU Leuven Datasets API
The Datasets API from KU Leuven — 92 operation(s) for datasets.
KU Leuven Datatags API
The Datatags API from KU Leuven — 1 operation(s) for datatags.
KU Leuven DataverseFeaturedItems API
The DataverseFeaturedItems API from KU Leuven — 1 operation(s) for dataversefeatureditems.
KU Leuven Dataverses API
The Dataverses API from KU Leuven — 39 operation(s) for dataverses.
KU Leuven Edit API
The Edit API from KU Leuven — 1 operation(s) for edit.
KU Leuven ExternalTools API
The ExternalTools API from KU Leuven — 2 operation(s) for externaltools.
KU Leuven Files API
The Files API from KU Leuven — 20 operation(s) for files.
KU Leuven Harvest API
The Harvest API from KU Leuven — 7 operation(s) for harvest.
KU Leuven Inbox API
The Inbox API from KU Leuven — 1 operation(s) for inbox.
KU Leuven Info API
The Info API from KU Leuven — 49 operation(s) for info.
KU Leuven Ingest API
The Ingest API from KU Leuven — 1 operation(s) for ingest.
KU Leuven Licenses API
The Licenses API from KU Leuven — 6 operation(s) for licenses.
KU Leuven Localcontexts API
The Localcontexts API from KU Leuven — 2 operation(s) for localcontexts.
KU Leuven Logout API
The Logout API from KU Leuven — 1 operation(s) for logout.
KU Leuven Mail API
The Mail API from KU Leuven — 1 operation(s) for mail.
KU Leuven Meta API
The Meta API from KU Leuven — 2 operation(s) for meta.
KU Leuven Metadatablocks API
The Metadatablocks API from KU Leuven — 2 operation(s) for metadatablocks.
KU Leuven Mydata API
The Mydata API from KU Leuven — 1 operation(s) for mydata.
KU Leuven Notifications API
The Notifications API from KU Leuven — 6 operation(s) for notifications.
KU Leuven Pids API
The Pids API from KU Leuven — 6 operation(s) for pids.
KU Leuven replaceFilesInDataset API
Replace a file to a dataset
KU Leuven Roles API
The Roles API from KU Leuven — 3 operation(s) for roles.
KU Leuven saveAuxiliaryFileWithVersion API
Save Auxiliary File With Version
KU Leuven Search API
The Search API from KU Leuven — 2 operation(s) for search.
KU Leuven Sendfeedback API
The Sendfeedback API from KU Leuven — 1 operation(s) for sendfeedback.
KU Leuven uploadDatasetLogo API
Uploads a logo for a dataset
KU Leuven Users API
The Users API from KU Leuven — 10 operation(s) for users.
KU Leuven Workflows API
The Workflows API from KU Leuven — 1 operation(s) for workflows.
Scroll within the panel for all 41 ·
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.
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.
Ku Leuven 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.
Ku Leuven 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.
Ku Leuven 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.
KU Leuven API Rules
SPECTRALKU Leuven API Rules
SPECTRALJSON Schema 4
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.
KU Leuven RDR DataFile
JSON SCHEMAKU Leuven RDR Dataset
JSON SCHEMAKU Leuven RDR DatasetVersion
JSON SCHEMAKU Leuven RDR Info Version Response
JSON SCHEMAJSON 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.
Ku Leuven Datafile Structure
JSON STRUCTUREKu Leuven Dataset Structure
JSON STRUCTUREKu Leuven Datasetversion 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.
Ku Leuven Dataset Example
EXAMPLESecurity 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 KU Leuven — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
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/ku-leuven · machine-readable index on apis.io